← previous blocknext block →recent activity
Analyzing
Block #82,048,459
14 transactions · 13 stateful · 2026-06-18 07:42:59 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,048,459 · 14 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
1w02w03w04w15w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x76d1e78d…7877
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x31d25d09…2151
0xa6afd3…d132
3 touches
1 conflict
0x61ea0cc4…735f
0x40c49f…2af0
2 touches
0 conflicts
0x40970e69…da50
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
10 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity