pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,941
13 transactions · 10 stateful · 2026-05-04 15:06:50 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,399,941 · 13 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
1w02w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xf335007f…4d0e
0x065c9d…c394
4 touches
1 conflict
0x59b50479…8019
0x065c9d…c394
4 touches
1 conflict
0xc8113c35…021c
0x065c9d…c394
3 touches
1 conflict
0xe4fc46c5…3d36
0x065c9d…c394
3 touches
1 conflict
0x897b34fc…f9a1
0x065c9d…c394
2 touches
0 conflicts
0xc240546d…0c46
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