← previous blocknext block →recent activity
Analyzing
Block #80,246,772
11 transactions · 7 stateful · 2026-06-09 23:34:00 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,246,772 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x4e499b7c…52ae
0x065c9d…c394
2 touches
0 conflicts
0x566374ad…53be
0x065c9d…c394
2 touches
0 conflicts
0x759e9124…1381
0x065c9d…c394
2 touches
0 conflicts
0x7c7c29e6…1b97
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xacef900b…155b
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity