← previous blocknext block →recent activity
Analyzing
Block #85,136,068
17 transactions · 16 stateful · 2026-07-02 15:08:41 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,136,068 · 17 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
1w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x2ae779cb…3839
0x065c9d…c394
3 touches
1 conflict
0xdbcceb7f…1ea1
0x065c9d…c394
3 touches
1 conflict
0x79213c55…f39d
0x065c9d…c394
2 touches
0 conflicts
0xb6a31785…afa4
0x065c9d…c394
2 touches
0 conflicts
0xdcf53dbb…7e43
0x065c9d…c394
2 touches
0 conflicts
0xfa7f7e41…4a91
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