← previous blocknext block →recent activity
Analyzing
Block #73,917,412
11 transactions · 11 stateful · 2026-05-11 15:45:43 UTC
Parallelism
55/100
Blocked
55%
Avg conflicts / tx
1.09
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,917,412 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
8 touches
6 conflicts
0x23951077…539b
0x34b655…2a6f
6 touches
3 conflicts
0x621ccd6b…83df
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
6 touches
3 conflicts
0x578e7f66…1b56
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x8a85cf3d…2868
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
6 conflicts on slot 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity