pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,211,462
← previous block
next block →
recent activity
Analyzing
Block #76,211,462
9 transactions · 9 stateful · 2026-05-22 06:58:23 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,211,462
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#5
executeBatch
#6
updateDataFeedsValuesPartial
#7
setData
#8
execOrders
#2
0xab083028
· blocks 2
#3
batchUpdate
#4
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x3a6e7600…e1f1
0xa6afd3…d132
4 touches
1 conflict
0xdb9d8189…e926
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1d0dd7f4…63ed
0x065c9d…c394
2 touches
0 conflicts
0x3e23b56f…bb78
0x065c9d…c394
2 touches
0 conflicts
0x7d6b0ecd…6490
0x065c9d…c394
2 touches
0 conflicts
0x7ea93017…ebbf
0x065c9d…c394
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x99a2130578…57dffc
Audit this contract →
← previous block
·
next block →
recent activity