← previous blocknext block →recent activity
Analyzing
Block #72,973,791
16 transactions · 13 stateful · 2026-05-07 06:50:02 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,973,791 · 16 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
1w05w16w07w111w212w313w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7f189cf6…afab
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x0eac6378…36f4
0x34b655…2a6f
6 touches
3 conflicts
0x8e6d14b7…b361
0x34b655…2a6f
6 touches
3 conflicts
0xf4730a2d…3538
0x34b655…2a6f
6 touches
3 conflicts
0xdd8d1a99…e1da
0x34b655…2a6f
4 touches
1 conflict
0x150af51d…9c42
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity