← previous blocknext block →recent activity
Analyzing
Block #82,585,766
13 transactions · 9 stateful · 2026-06-20 19:27:55 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,585,766 · 13 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
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0xba7cf98a…8407
0x065c9d…c394
3 touches
1 conflict
0xee276e9e…8e47
0x065c9d…c394
3 touches
1 conflict
0x5a900395…4eb6
0x065c9d…c394
2 touches
0 conflicts
0x9e326f16…6a6d
0x065c9d…c394
2 touches
0 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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
1 conflict on slot 0x557cd4fad5…e4228c
Audit this contract →
← previous block·next block →recent activity