pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,514,094
← previous block
next block →
recent activity
Analyzing
Block #73,514,094
12 transactions · 9 stateful · 2026-05-09 18:45:10 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,514,094
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xed82b078
· blocks 1
#4
0x69ff812e
#5
0xec2bd3f2
#6
0xed82b078
#7
0xed82b078
#8
settle
#9
updateDataFeedsValuesPartial
#10
0x69ff812e
#11
setData
#3
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1151b256…b43b
0x09475a…400f
2 touches
0 conflicts
0x3d4d8630…d9e3
0x09475a…400f
2 touches
0 conflicts
0x88c7bc1a…32a8
0x09475a…400f
2 touches
0 conflicts
0xee2e48fa…c427
0x09475a…400f
2 touches
0 conflicts
0x107eeecc…2285
0x607560…d0f5
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: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity