← previous blocknext block →recent activity
Analyzing
Block #73,808,116
9 transactions · 8 stateful · 2026-05-11 03:37:38 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,808,116 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x8240d70c…7c3b
0x34b655…2a6f
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x8799b422…7fc1
0x065c9d…c394
2 touches
0 conflicts
0x8874297d…9990
0x065c9d…c394
2 touches
0 conflicts
0xdc48b5c6…9b60
0x065c9d…c394
2 touches
0 conflicts
0xe6bb09fe…e6b6
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity