← previous blocknext block →recent activity
Analyzing
Block #80,250,610
12 transactions · 11 stateful · 2026-06-09 23:59:34 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,250,610 · 12 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
2w03w14w25w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x68eeb767…d64f
0x065c9d…c394
4 touches
1 conflict
0x0690f2e6…d37f
0x065c9d…c394
3 touches
1 conflict
0x5a37ba28…e31d
0x40c49f…2af0
3 touches
1 conflict
0xe9bd979b…40ca
0x40c49f…2af0
2 touches
0 conflicts
0xf30ed5ce…608a
0x40c49f…2af0
2 touches
0 conflicts
0x213ee207…a151
0x69df8a…6292
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
6 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity