← previous blocknext block →recent activity
Analyzing
Block #73,967,690
11 transactions · 9 stateful · 2026-05-11 21:20:09 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,967,690 · 11 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
1w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x16b3793f…20f7
0x065c9d…c394
2 touches
0 conflicts
0x170fa91e…8f7e
0x065c9d…c394
2 touches
0 conflicts
0x262121f3…221b
0x065c9d…c394
2 touches
0 conflicts
0x45512696…ee00
0x065c9d…c394
2 touches
0 conflicts
0x94d36245…e1b6
0x065c9d…c394
2 touches
0 conflicts
0xaed83ac8…6b1e
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