← previous blocknext block →recent activity
Analyzing
Block #72,310,682
13 transactions · 11 stateful · 2026-05-04 05:12:08 UTC
Parallelism
69/100
Blocked
55%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,310,682 · 13 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
2w03w16w07w18w29w210w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b7bcac3…8fbf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x3254d19b…f714
0x34b655…2a6f
4 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
4 touches
1 conflict
0x50a8f964…ded5
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: Perpl
3 conflicts on slot 0x7b7bcac3fe…968fbf
Audit this contract →
← previous block·next block →recent activity