pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,571,482
10 transactions · 9 stateful · 2026-05-05 10:09:11 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,571,482 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6bbe7a63…4500
0x065c9d…c394
4 touches
1 conflict
0x41d765cf…3d31
0x065c9d…c394
4 touches
1 conflict
0xe9dfd0ec…eb32
0x065c9d…c394
3 touches
1 conflict
0xd521d793…82ad
0x065c9d…c394
3 touches
1 conflict
0x73bce881…1ceb
0x065c9d…c394
3 touches
1 conflict
0xaa31e4c8…ff18
0x065c9d…c394
3 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity