← previous blocknext block →recent activity
Analyzing
Block #80,820,723
17 transactions · 15 stateful · 2026-06-12 15:21:10 UTC
Parallelism
65/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,820,723 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xfd72a574…e07a
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
3 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x02548f76…aad6
0x40c49f…2af0
2 touches
0 conflicts
0x0b132f26…8927
0x40c49f…2af0
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity