►
Description
Follow the latest from NEAR Protocol on:
Website: https://near.org/
Discord: https://near.chat/
Blog: https://near.org/blog/
Twitter: https://twitter.com/NEARProtocol
GitHub: https://github.com/near https://github.com/nearprotocol
#Blockchain #FutureIsNEAR #NEAR #nearprotocol
A
Yeah,
okay,
so
froel
thanks
again
for
taking
the
time
to
walk
us
through
the
rpc
api
and
this
time
from
the
perspective
of
the
near
explorer.
So
I
think
what
we've
agreed
is
we're
going
to
talk
about.
How
do
we
build
up
this
interface
of
near
explorer?
Actually
and
you'll?
Give
us
a
tour
of
this
kind
of
sweeping
through
the
the
different
data
that
we
see
where
it's
coming
from
to
help
us
make
sense
of
how
we're
using
the
rpc
api
to
produce
this
interface
here.
B
Yeah
sure
no
problem
we
have,
if
you
open
the
website,
you
immediately
grid
it
with
this
nice
page
with
the
dashboard
and
the
search
and
main
bar,
let's
go
from
from
the
top
to
the
bottom,
just
to
understand
better
what
other
tools
that
you
can
use
here
here
we
have
the
network
selection
current.
Currently,
the
explorer
is
deployed
for
mainnet
and
testnet,
and
whenever
you
switch,
you
just
select
the
network
and
this
their
interface
is
the
same.
It
is
just
the
data
that
is
different
based
on
the
network
selected
on
the
right.
B
You
have
more
deep
down
a
breakdown
into
different
pages
that
you
could
be
interested
in
blogs
and
transactions
unnatural
to
near
protocol
accounts
is
aggregate
about,
like
what
are
the
accounts
essentially
are
currently
active
or
deleted,
and
the
notes
is
the
page
where
you
would
navigate
and
see
more
about
the
network
itself
about
the
archival
nodes,
validation,
nodes,
other
types
of
services
that
are
also
in
the
peer-to-peer
network
of
near
so
keep
keep
keeping
going
on
the
on
this
main
page.
B
You
can
see
that
the
torch
is
the
main
part
of
the
page
and
that's
on
purpose.
It's
very
hard
to
navigate
and
find
to
a
specific
block
or
specific
transaction
in
the
list.
It's
much
better.
If
you
have
your
account
id
or
any
transaction
that
you
want
to
explore,
you
just
dump
it
here.
Click
search,
you're
there
exploring
it
so
search,
is
a
very
core
feature
and
we
encourage
people
to
use
it
or
there.
It's
just
a
lot
of
nice
graphs
and
overall
stats
about
the
state
of
the
network.
B
Let's
go
one
by
one
here,
so
the
nodes
is
essentially
representing
the
health
of
the
network
itself.
It's
very
important
to
have
as
many
validator
validating
nodes
as
possible.
They
are
ensuring
the
security
of
the
data
and
that's
why
it's
great
that
we
have
so
many
of
them
right
now.
Online
notes.
It's
all
those
for
leading
nodes
plus
those
who
are
using
a
near-core.
B
Network
near-core
software
to
essentially
get
access
to
the
data.
One
of
the
examples,
like
a
few
of
the
examples,
would
be
json
rpc
nodes.
They
are
not
like
validating
nodes,
does
not
expose
json
or
pc
to
the
public
just
for
the
security
reasons.
So
instead,
what
is
suggested
is
to
always
have
rpc
nodes
in
front
of
your
validating,
node
and,
in
other
instances,
would
be
archival
nodes
which
keep
track
of
all
the
history
from
very
beginning
of
the
network
from
genesis.
B
Also,
another
example
is
indexer
nodes
which
we,
one
of
them
is
used
for
explorer
itself.
So
a
lot
of
them
are
here.
We
will
open
up
them
once
we
cover
the
rest
of
the
page,
so.
A
Sorry,
so,
just
just
to
summarize
what
I
heard
you
say
there,
because
this
wasn't
obvious
to
me
when
we
first
talked
about
it.
So
there's
60,
validating
nodes
and
best
practice
is
each
one
of
these
60
validating
nodes
should
also
have
an
rpc
node
sitting
in
front
of
it.
So
that's
that's
120
of
the
186
right
there.
A
If
people
are
doing
what
we're
asking
them
to
do
right,
then
there's
the
balance
of
60
65
66
other
nodes
that
these
these
are
indexing
nodes,
including
you
know
these
are
the
kinds
of
nodes
that
are
listening
to
the
network
and
letting
us
query
it,
maybe
using
a
database
or
something
and
then
archival
nodes
are
like
an
indexing
node,
but
it's
not
for
querying
purposes.
It's
just
for
archival
purposes.
So
so
the
the
nature
of
what
the
node.
A
Yeah,
it's
a
backup
node,
and
it
is
that
are
those
basically,
the
three
sort
of
three
four
classes:
validating
nodes
that
are
actively
maintaining
security
and
integrity
of
the
network.
Rpc
nodes
that
are
sitting
right
in
front
of
them
by
recommendation
indexing
nodes
and
archival
nodes.
Are
there
any
other
nodes
that
are
running
on
the
network.
B
B
B
Blogs
is
in
core
nature
when
you
blockchain
you
produce
block
every
second,
and
here
is
just
a
simple
stat,
exposing
us
to
what
is
the
latest
blockade
right
now
and
whether
the
network
is
doing
fine
so
and
usually
you
you
would
see,
numbers
are
almost
identical
all
the
time
here.
Next,
the
transactions.
This
section
is
quite
interesting
in
terms
of
like
to
to
understand
how
the
network
is
used,
because
blocks
are
produced,
no
matter
what,
but
the
transactions
essentially
represent
how
the
network
is
like
used
by
the
end
users
or
other
entities.
B
It
would
be
programmatic
use,
sometimes
it's
just
ping
or
oracle
request
to
the
network.
Sometimes
they
are
transfers.
So
all
kinds
of
transactions
are
floating
in
the
system,
so
here
the
latest
24
hours,
total
and
and
also
14
day
history.
We
exclude
today
from
the
history
just
because
it
would
be
always
a
drop
here
that
makes
sense
to
display
it,
and
it's
useless
and
gas
prices
here
is
essentially
to
represent
how
what
is
a
current
price
to
to
to
pay
for
a
gas
on
the
network.
A
We
have
an
article,
we
have
an
article
in
the
documentation
that
talks
about
you,
know
thinking
and
gas.
What
this
number
means
why
we
say:
terror,
gas.
It's
a
little
bit
easier
to
reason
about
than
you
know
some
some
of
the
large
numbers
that
we're
talking
about
you
just
use
the
prefix
terra
gas,
and
it
tells
everything
you
need
to
know.
I'm
surprised
to
see
gas
price.
A
You
know
kind
of
featured
so
prominently
like
this,
but
I
think
it's
because
of
of
the
way
that
we
we
price
gas,
it
actually
fluctuates.
Doesn't
it.
B
I
well
it
it
does
not
right
now.
It
will
eventually
with
a
greater
load
of
network
right
now,
it's
constant
and
actually
I'm
considering
to
replace
it
with
the
average
transaction
fee,
which
makes
more
sense
to
the
end
users
after
all,
and
it
just
hasn't
been
done
yet.
That's
the
only
reason.
B
I
also
agree
it's,
it's
not
the
best
metric
to
be
so
prominently
exposed,
but
I.
A
B
A
B
A
B
It's
it's
stable,
it's
well
tested
and
we
don't
expect
any
unknowns,
whereas
the
sharding
is
a
bit
complex
thing
and
it
needs
to
be
more
thoroughly
tested,
and
I
know
that
core
team
is
currently
making
sure
that
it's
solid
and
stable
and
it's
a
very
important
part
of
future
development.
A
Let's
talk
a
little
bit
about
how
this
data
is
getting
rendered
into
the
interface
here,
so
the
the.
If
we,
if
can
we
go
back
to
the
home
page,
just
the
main
kind
of
view
of
this
aggregate,
so
just
to
get
an
idea
that
the
search
bar
is
is
using
the
indexing
service
right
because
we
have
the
historical
data
there
and
in
fact,
a
lot
of
this
data
that
we
saw,
maybe
in
the
the
other
page
as
well,
is
coming
from
the
indexing
service.
B
A
With
data
as
it's
listening,
and
so
all
that
makes
sense,
and
can
you
tell
me
a
little
bit
about
some
of
these
other
numbers
like?
Where
are
you
getting
the
number
of
nodes
online?
Where
are
you
getting
the
number
of
validators
those,
I
think
should
be
available
in
the
rpc
api
right.
B
Here
here
yeah
the
valve
validator
status,
you
will
be
returned
with
current
voltage
released
and
if
you
count
the
number
of
this
records,
you
will
get
the
number
60..
B
If
you
open
the
page,
you
will
see
the
same
list
essentially
displayed
here,
render
it
with
all
the
detailed
information
how
many
blogs
they
have
produced,
how
many
blogs
they
are
expected
to
have
been
produced.
All
of
that
is
here.
B
A
B
B
A
Yeah
the
nodes
are
are
telling
us
that
they're
online,
so
we
we
know
one
there's
at
least
186
nodes
online.
There
may
be
many
more
right,
and-
and
so
that's
but
that's
being
reported
to
what
exactly
to
some
some
other
endpoint
that
that
explorer
expo.
A
B
Supporting
their
version,
they
are
agent,
their
latest
blog
and
all
all
the
rest
info,
and
we
just
record
when
we
heard
from
them
and
update
us
in
our
database
in
explorer.
B
Yep
current
proposals
yeah
over
here
so
yeah.
A
B
It's
essentially
a
representation
of
where
the
nodes
are
located
on
the
the
map.
How.
B
When,
when
the
online
nodes
report
to
us,
we
can
part.
B
A
B
Reporting
we
couldn't
really
display
them
on
the
map,
but
online
notes
all
186
we
could
we
can
represent
them,
though
some
of
them
are
off
sometimes
they're
reporting,
some
weird
locations
or
default
ones.
Where
it's
it's
it's
a
bug
and
we
should
filter
them
out.
Just
keep
in
mind.
B
Okay,
it's
just
a
for
representation.
Point
of
view
like
to
to
see
how
distributed
is
a
network.
We
currently
don't
see
anybody
on
the
on
this
hemisphere,
nor
in
australia,
nor
in
south
america
and
africa
is
also
underrepresented.
A
B
Factories
of
like
computer
power
are
not
really
built
in
in
africa
due
to
like
very
unstable
internet
connection
and
all
other
reasons
so,
but
okay
overall,
it's
distributed
pretty
widely
across
the
globe.
A
Yeah
I
mean
this
makes
sense.
So
if,
if
we
go
back
to
the
main
page,
we've
now
covered,
excuse
me
the
search
nodes.
We
looked
at
blocks
briefly
there
can
we
can
we
dig
into
a
block?
Can
we
see
in
more
detail
about
a
block
in.
B
This
case,
let
me
find
some
block
with
at
least
one
transaction,
so
it's
not
temperature,
so
here's
block
every
block
so
blocks
are
producers
said
no
matter
what
and
we
can
see
that
the
transactions
here
are
in
the
block
listed
here.
You
can
create
this
data
through
json
or
pc,
but
we
still,
but
we
prefer
to
use
our
own
indexed
data
anyway,
since
it's
already
in
our
database.
Why
would
we
request
it
again
and
again
from
the
rtc.
B
Yeah,
I
believe
so,
maybe
well
we
what
what
we
check
is
the
status
so
to
understand
whether
the
block
is
finalized.
B
B
With
the
finality
final
as
a
parameter
and
in
response,
I
will
get
all.
A
B
A
A
Is
greater
yeah
that
makes
sense,
there's
nothing
else
here
being
rendered
about
this
block
besides
the
list
of
transactions,
but
but
the
response,
the
payload
that
comes
back
from
this
block
details,
it's
quite
extensive,
there's
a
lot
going
on
there
is.
Is
there
is
there
more
to
talk
about
there?
Do
you
think,
or
is
it
out
of
scope
for
this
conversation.
B
Well,
mostly,
it's
references
to
next
and
previous
in
the
state
and
the
various
other
parts
of
the
network.
Timestamp.
Is
there
when
well.
Random
is
like
internal
thing.
It's
quite
interesting
topic
by
itself
how
we
deal
with
random
numbers,
but
it's
a
very
different
one.
I
don't
think
it's
available
on
explorer
side.
B
Gas
prices
is
there
yeah?
Overall,
I
wouldn't
say
that
there
is
something
that
is
missing.
We
could
provide
more.
You
know
advanced
features
just
for
the
sake
of
like
blockchain
developers
themselves,
but
from
the
user
perspective
I
guess
that's
all
that
is
really
interesting.
B
Maybe
chart
and
trunks
could
be
exposed,
but
we
decided
to
ignore
the
fact
that,
like
no
not
ignore
but
essentially
height
and
fact
that
we
are
having
charts
in
the
system
what
we
believe
that
people
mostly
care
about
blocks,
even
even
that
is
already
controversial
whether
they
really
need
to
know
about
the
blocks
and
about
the
transactions
themselves.
Everything
else
is
implementation.
Detail,
that's
why
we
decided
to
just
skip
it
and
unload
the
end
user
from
knowing
all
the
details
about
the
implementation
itself.
B
Okay,
yeah
right
on
yeah,
so
and
just
to
finish
up
the
core
concepts.
If
you
go
and
open
the
list
of
transactions
page,
you
can
see
that
there
are
transactions
here
in
a
ordered
by
the
time
that
they
occurred
in
the
network.
Again,
as
we
had
already
covered
it,
it's
all
sitting
in
the
database.
You
can't
quit
it
through
json
or
pc,
so
we
needed
to
index
this
data
through
going
through
every
single
block
and
save
the
data
in
our
own
database,
specifically
for
exploring
needs,
and
this
way
you
can
answer.
B
The
question
like
give
me
last
10
transactions
here,
and
here
we
go.
The
same
goes
for
whenever
you.
So
when
we
open
a
transaction
itself,
it's
all
great!
It's
it's
still
under
construction.
Here
we
are
building
better
ui
to
represent
the
internals.
So
let's
not
focus
on
this
right
now,
as
it
will,
change
in
this
quarter
quite
drastically
and
represent
the
data
better.
But
what
is
essentially
about
the
transaction
that
the
core
thing
is
that
every
transaction
has
assigned
already
the
signer
account
id
and
receiver
account
id.
B
We
estimated
status
it's
a
bit
of
a
different
topic
and
it's
not
focusing
right
now.
Transaction
fee
is
probably
what
most
of
the
people
might
be
interested
in
terms
of
like
estimating
how
much
it
costs.
Currently,
it's
quite
a
small
number,
even
for
very
complex
transactions,
if
it's
just
a
transfer
call
it's
even
smaller
and
the
like.
Well,
deposit
value
is
also
quite
interesting
thing.
When
you
call
a
function
method,
sometimes
you
can.
You
want
to
pay
for
for
the
transaction
here.
B
Hashes
are
useful,
but
you,
as
a
user
as
a
human,
did
not
really
make
a
lot
of
sense
out
of
them.
They
mostly
are
useful,
for
you
know
the
reference
purposes
and
to
make
sure
that
you
are
looking
exactly
on
the
same
thing
that
you
expect
to
look
at
if
somebody
is
like
sending
you
a
link
or
or
whatnot.
B
So
that's
all
about
the
transaction
itself
and
all
the
all
the
info
about
the
transaction.
If
you
have
a
transaction
hash
and
know
the
receiver
id,
you
can
look
it
up
through
json
pc.
B
Transaction
hash
is
enough
to
to
look
up
the
transaction
in
other
systems,
but
given
the
sharding
nature
of
lanier,
the
transaction
will
end
up
on
the
chart
where
the
account
belongs
to
and
that's
why
to
look
up
the
transaction.
You
need
to
specify
some
some.
You
need
to
have
some
way
to
specify
which
chart
you
need
to
go
to
that's
why
whenever
you
look
up
through
json
rpc
tx
status
send
nope
transaction
status
here
here
we
go,
you
need
to
specify
the
hash
and
the
what's
this
hash
of
fruit.
B
So
whenever
you
submit
a
transaction,
do
we
talk
about
it?
Much
not
really.
So,
when
you
construct
a
transaction
on
on
your
side
and
sign
it,
you
sign
the
hashes
transaction
hash
itself.
Your
signature
confirms
that
the
hash
represents
the
data
that
is
passed
next
to
it,
and
this
hash
can
be
later
in
throughout.
The
history
can
be
used
as
a
reference
to
the
transaction.
A
I'm
I
guess,
I'm
I'm,
I'm
a
little
bit
confused
why
you
would
also
need
to
specify
the
receiver
account.
I
mean
I
understand
in
a
sharded
environment
that
maybe
center.testnet
would
be
on
its
own
shard
separate
from
you
know,
some
other
account
but
you're
saying
that
there's
no
way
to
kind
of
globally
search
for
this
transaction
hash.
You
can
only
search
for
it
on
this
shard
because,
because
not
shards
don't
know
about
each
other,
actually
they're
they're,
essentially
running
in
parallel
right.
That's
how
we're
getting
this!
B
Exactly
so
the
transaction
is
I
I
was,
I
was
misleading
previously.
I
was
telling
you
that
the
transaction
ends
up
on
the
receiver
side.
Essentially
it's
now,
it's
the
the
receipts
are
on
the
receiver
side,
but
introduction
are
always
belong
to
to
the
signer.
That's
where
it
starts
its
journey
to
start
executing
the
transaction.
You
need
to
first
deliver
that
this
transaction
to
the
chart
where
the
signer
account
is
stored
to
verify
the
signatures.
B
B
And
this
way
we
can
look
it
up
so
internally
to
look
it
up.
We
need
to
specify
the
sender,
but
in
explorer,
as
you
can
see,
you
can
navigate
to
the
page
only
providing
the
transaction
hash.
It
is
possible
only
because
we
have
our
own
indexing
backhand,
which
goes
up
through
every
single
transaction.
We
store
all
the
transactions
in
a
single
database.
A
Is
there
some
way
to
change
the
representation
random
thought
by
or
have
we
considered
changing
the
representation
of
of
this
data?
That's
rendered
on
this
page
by
appending
something
like
dot
json
to
the
url,
so
so
that
when
we
request
it
from
the
explorer,
it
sends
back
a
json
response
of
this
data
as
opposed
to
the
rendered
html.
B
A
B
I'm
a
bit
you
know
concerned
with
such
features
because
it
may
create
unnecessary
incentive
in
terms
of
like
people
will
rely
on
explorer
too
much.
B
Yeah,
as
opposed
to
using
like
the
decentralized
to
comply
with
decentralized,
you
know
network
and
I'm
a
bit
afraid
to
let
people
down
that
way
and
if
explorer
will
be
so
much
in
like
central
service
for
every.
For
for
everything,
we
may
lose
the
whole
app
layer.
A
B
So
what
else
we
covered
transactions.
B
Yeah
we
can
also
go
to
the
last
piece.
Probably
the
account
account
page
is
essentially
also
relies
on
the
data
that
we
collect
throughout
the
history
through
analyticser,
we
have
transactions,
you
you
see,
I
open
the
account
and
I
immediately
see
the
transactions
that
happened
months
ago.
B
A
B
Oh
yeah,
it's
well,
we
had
a
lot
of
discussions
here
and
people
are
getting
more
and
more
confused
with
the
balances
and
it's
not
no
surprise
even
internally.
Sometimes
we
refer
to
the
same
thing
using
different
terms
and
what
people
tend
to
want
to
see
whenever
they
navigate
to
their
own
account
is
the
their
balance.
B
It's
on
the
one
balance
right.
Why
do
I
have
several
ones?
I
I
just
I
just
want
to
have
one
but
naturally
and
near
is
built,
is
a
low
level
platform
with
high
level
concepts
built
as
a
like
extensions
from
the
application
level
level.
So
it's
we
provide
certain
tooling
and
the
balances
that
are
in
here
in
in
near
protocol.
B
A
So
it's
we're
saying
native
account
balance
because
there's
there's
you've
broken
this
out
into
three
places
right.
So
there's
the
the
two
parts,
the
what
you
can
spend
today,
what
you're
staking
and
then
some
aggregate
of
those
two.
Those
are
the
three
views.
B
Here:
well,
it's
not
the
aggregate
of
these
two,
it's
an
aggregate
of
potentially
more
other
contract.
More
other
accounts
which
are
in
the
connection,
for
example,
lock
up
contract,
is
a
as
a
sep.
It's
a
separate
account
right.
A
B
You
see
if
we
open
another
account
which
has
a
lockup
account.
We
display
the
lockup
here
you
can
navigate
there.
You
can
see
that
it
has
its
own
native
account
balance
we.
What
what
people
tend
to
expect
is
to
have
a
sum
of
this
value,
plus
this
value,
plus
the
the
account
could
have
delegated
certain
amount
to
the
staking
pool.
Then
it
means
that
we
need,
to
sum
also
the
tokens
from
the
sticking
pool
and
it's
it's
very
complex,
to
pull
together
and
that's
why
we
tried
to
do
it.
B
B
B
Let
explorer
only
focus
on
the
native
thing
that
we
expose
through
the
protocol
and
wallet
deal
with,
like
all
the
rest,
like
you
can
see
here
that
the
nexus
account
has
this
amount
of
tokens.
Some
of
them
are
reserved.
B
Then
the
same
goes
for
lockup
again,
so
it's
nice
breakdown,
a
much
cleaner
representation,
and
we
couldn't
make
it
on
this
on
this
page
with
the
current
design,
it
should
have
been
redesigned
anyway
to
something
like
this
to
have
a
breakdown
which
would
be
which
would
make
sense
to
the
end
users.
After
all,.
A
Yeah,
so
I
think
I
I
think
I
get
it
in
the
end,
you're
saying
from
the
wallet
perspective
you're,
seeing
the
account
that
you
control
and
any
other
sort
of
you
know
con
contract
level,
assets
that
are
controlled
by
this
account.
So
that's
the
view
from
the
wallet
from
the
explorer
you're
talking
about
sort
of
the
native
token
that
this
account
is
holding-
and
I
guess
maybe
also
a
lockup
account,
but
there's
no
room
here
for
multiple
lock-up
accounts.
A
So
it
it
makes
sense
that
we're
sort
of
keeping
this
focused
on
the
account.
As
you
know,
some
you
know
from
the
account
perspective,
you
know
on
the
network
an
account
that
engages
in
transactions
and
transaction
history.
That
makes
sense.
You
can
see
that
this
account
has
sent
72
transactions
or
signed
72
transactions,
maybe
received
one
something
like
that,
whereas
from
the
wallet
it's
about
asset
management,
you
know
what
what
lock
up
accounts
you're
connected
to
and
all
that
sort
of
stuff
that
makes
sense.
Yeah.
B
Yeah,
so
that's
all
what
I
wanted
to
cover
with
the
the
balances
also,
as
we
might
have
seen
in
the
docs,
when
you
view
account
query,
you
see
the
balance.
So
this
is
a
native
balance
essentially,
and
this
is
a
state
balance
and
validator
validators
take
balance.
B
These
are
the
two
values
that
we
are
connecting
from
json
rpc
response
to
the
explorer
ui
storage
used
is
here:
storage
usage,
essentially
yeah,
it
just
bytes
and
it's
300
358
kilobytes,
and
it's
coming
from
the
contract
that
we
deployed
on
the
account
what
else.
B
B
Yeah,
that's
what
wallet
talks
360k
there
yeah,
as
you
can
see
three
five:
eight:
zero,
seven,
three
nine
and
it's
exactly
the
number
we
see
here
so
correct
at
least.
Currently
we
are
the
new
version
which
may
lower
the
cost
and
it
could
be
just
a
different
different
number.
But
it's
right
now.
It's
very
easy
to
observe
how
the
storage
usage
is
connected
with
the
minimum
balance.
A
Yeah
yeah
and
that's
basically
reserved
until
you
reduce
the
storage
on
the
account.
Then
it's
unlocked,
you
can
do
whatever
you
want
with
it
yeah
that
makes
sense.
Okay,
I
feel,
like
we've
covered
quite
a
bit
here.
Is
there
anything
else
that
we
should
include?
In
this
I
mean
we've
kind
of
gone
over
all
the
interfaces,
maybe
in
the
explorer
touched
a
little
bit
on
the
wallet
as
well.