← previous blocknext block →recent activity
Analyzing
Block #85,173,322
19 transactions · 17 stateful · 2026-07-02 19:16:45 UTC
Parallelism
84/100
Blocked
18%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,173,322 · 19 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
1w02w15w27w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x3827ba8b…81f9
0xd32edf…ff58
3 touches
1 conflict
0x21606e27…9e78
0x065c9d…c394
2 touches
0 conflicts
0x2e718943…4075
0x065c9d…c394
2 touches
0 conflicts
0x4a91d79c…77f1
0x065c9d…c394
2 touches
0 conflicts
0x51e72ea8…b7f7
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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity