pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,576,401
10 transactions · 9 stateful · 2026-05-05 10:41:58 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,576,401 · 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
1w02w14w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeaba4491…5d92
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x619ff86e…f233
0xd32edf…ff58
3 touches
1 conflict
0x59b662d6…2ac7
0x065c9d…c394
3 touches
1 conflict
0xa777c06e…13b2
0x065c9d…c394
3 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
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 0xeaba449187…d85d92
Audit this contract →
← previous block·next block →recent activity