← previous blocknext block →recent activity
Analyzing
Block #85,823,966
10 transactions · 10 stateful · 2026-07-05 19:30:52 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,823,966 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xd7007684…1b3f
0x065c9d…c394
3 touches
1 conflict
0xd89afc07…0aa4
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x39d2996f…aa8f
0x40c49f…2af0
2 touches
0 conflicts
0xfb228bc3…19a4
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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity