← previous blocknext block →recent activity
Analyzing
Block #73,982,597
9 transactions · 7 stateful · 2026-05-11 23:00:12 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,982,597 · 9 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
1w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xee230b20…5a0f
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x17dc7cd4…6e9d
0x34b655…2a6f
2 touches
0 conflicts
0x2aef4269…ad47
0x34b655…2a6f
2 touches
0 conflicts
0x3c6cf955…1112
0x34b655…2a6f
2 touches
0 conflicts
0x48309067…573e
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x1b9e654ec8…aa0a08
Audit this contract →
← previous block·next block →recent activity