pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,628,914
← previous block
next block →
recent activity
Analyzing
Block #87,628,914
13 transactions · 9 stateful · 2026-07-14 04:33:51 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,628,914
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
updatePosition
#5
execFwdPositionOps
#6
forward
#8
0x6a55bca7
#9
setData
#10
0x911a52…e399
#11
0x4d04f1…9408
#12
0xd4bcda…794b
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78346476…4311
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x96efe05d…5d48
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x158622…375e
2 touches
0 conflicts
0x2e0517d4…d18a
0x158622…375e
2 touches
0 conflicts
0x8a35acfb…d1ad
0x158622…375e
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0x7834647688…ce4311
Audit this contract →
← previous block
·
next block →
recent activity