← previous blocknext block →recent activity
Analyzing
Block #85,168,569
11 transactions · 9 stateful · 2026-07-02 18:45:08 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,168,569 · 11 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5de2fc85…7755
0x065c9d…c394
2 touches
0 conflicts
0x7803622f…4995
0x065c9d…c394
2 touches
0 conflicts
0x7e81d33c…508e
0x065c9d…c394
2 touches
0 conflicts
0x7f2b06ac…d6b1
0x065c9d…c394
2 touches
0 conflicts
0xb0c820d8…7665
0x065c9d…c394
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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity