pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,859,598
10 transactions · 8 stateful · 2026-05-06 18:10:03 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,859,598 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x4e5ebbf7…ae70
0xc8689a…ee79
6 touches
3 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…000b
0x6ca43f…c331
6 touches
3 conflicts
0x0175b7a6…1db9
0x6ca43f…c331
6 touches
3 conflicts
0x0175b7a6…1dbb
0x6ca43f…c331
6 touches
3 conflicts
0x0175b7a6…1dbd
0x6ca43f…c331
6 touches
3 conflicts
0x3e4b8d9f…b8a7
0x6ca43f…c331
6 touches
3 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: 0x065c9d28…a9c394
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity