← previous blocknext block →recent activity
Analyzing
Block #80,248,684
10 transactions · 9 stateful · 2026-06-09 23:46:45 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,248,684 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xcae32e34…1b64
0x40c49f…2af0
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x33e3eba6…6926
0x40c49f…2af0
2 touches
0 conflicts
0x4f3391cd…2ad1
0x40c49f…2af0
2 touches
0 conflicts
0x58a864a6…57e3
0x754704…b603
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: MarginAccount
3 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity