← previous blocknext block →recent activity
Analyzing
Block #73,328,694
11 transactions · 10 stateful · 2026-05-08 22:11:35 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,328,694 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3d3ee6b2…6223
0x065c9d…c394
2 touches
0 conflicts
0x469c9284…9db6
0x065c9d…c394
2 touches
0 conflicts
0x49b34aec…8550
0x065c9d…c394
2 touches
0 conflicts
0x5f1a05fc…823e
0x065c9d…c394
2 touches
0 conflicts
0x9e38f599…3a17
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 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity