pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,371,127
9 transactions · 9 stateful · 2026-05-04 11:54:44 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,371,127 · 9 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
1w02w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8a35acfb…d1ae
0x8d66a4…3095
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
0x126c25d0…0a94
0x065c9d…c394
2 touches
0 conflicts
0x45855fc6…68f6
0x065c9d…c394
2 touches
0 conflicts
0xa0d06272…7893
0x065c9d…c394
2 touches
0 conflicts
0xa46bf8a9…bfb6
0x065c9d…c394
2 touches
0 conflicts
0xb3e72a0c…588d
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity