pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,447,796
← previous block
next block →
recent activity
Analyzing
Block #76,447,796
13 transactions · 11 stateful · 2026-05-23 09:12:20 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,447,796
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
exactOutputSingle
#3
exactOutputSingle
#4
execute
#5
0xab083028
· blocks 2
#7
updateDataFeedsValuesPartial
#8
batchUpdate
#10
setData
#11
0xf2eaccd1
#12
execute
#6
0xab083028
· blocks 1
#9
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xa605468c…1bfc
0x1d1325…2305
4 touches
1 conflict
0xc8525006…2b45
0x1d1325…2305
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1fff6dcb…b3f4
0xc8689a…ee79
4 touches
1 conflict
0x06e40499…165e
0x1d1325…2305
4 touches
1 conflict
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: Market-MON/USDC
3 conflicts on slot
0x18cf3003ed…9951d1
Audit this contract →
← previous block
·
next block →
recent activity