pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,314,652
14 transactions · 12 stateful · 2026-05-04 05:38:33 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,314,652 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w19w210w312w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb9d2cf20…a668
0x34b655…2a6f
6 touches
3 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0xb8228d38…3953
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity