← previous blocknext block →recent activity
Analyzing
Block #80,484,125
11 transactions · 8 stateful · 2026-06-11 01:55:46 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,484,125 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x1b60b708…5b4b
0x69df8a…6292
3 touches
1 conflict
0xa5d738a0…062f
0x065c9d…c394
3 touches
1 conflict
0x5135e8ca…28f3
0x065c9d…c394
2 touches
1 conflict
0xb13540a3…5f6c
0x065c9d…c394
2 touches
1 conflict
0x2b709338…d472
0x69df8a…6292
2 touches
1 conflict
0x387e5d22…18ba
0x69df8a…6292
2 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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity