pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,572,728
8 transactions · 6 stateful · 2026-05-05 10:17:29 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,572,728 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3beebdb…bd62
0x065c9d…c394
4 touches
1 conflict
0xad138fd7…d5bb
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3c6a474a…137b
0x065c9d…c394
3 touches
1 conflict
0x3a680859…4c8f
0x065c9d…c394
3 touches
1 conflict
0xe75c04ba…55b3
0x065c9d…c394
3 touches
1 conflict
0x8960831f…4739
0x065c9d…c394
3 touches
1 conflict
0xd842d79e…9f89
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: 0x065c9d28…a9c394
1 conflict on slot 0xa3beebdb5b…c7bd62
Audit this contract →
← previous block·next block →recent activity