pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,795,919
← previous block
next block →
recent activity
Analyzing
Block #73,795,919
13 transactions · 9 stateful · 2026-05-11 02:15:44 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
#73,795,919
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0x6a013c48
#3
0x54cb092e
#4
0x6a013c48
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
0x0c7abd22
· blocks 1
#8
jMMeC
#10
forward
#11
forward
#12
setData
#9
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2528fadd…b3d3
0xd32edf…ff58
3 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:
0xd32edf66…9fff58
1 conflict on slot
0x2528fadd6d…afb3d3
Audit this contract →
← previous block
·
next block →
recent activity