← previous blocknext block →recent activity
Analyzing
Block #85,191,697
10 transactions · 9 stateful · 2026-07-02 21:19:08 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,191,697 · 10 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x34b1cb7c…2a78
0x065c9d…c394
4 touches
1 conflict
0xe4c8f93d…3396
0x065c9d…c394
3 touches
1 conflict
0xaa5403b2…6c13
0x065c9d…c394
3 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0xc161a410…c9b0
0x065c9d…c394
2 touches
0 conflicts
0xe2bead11…f38f
0x065c9d…c394
2 touches
0 conflicts
0xed7b0c9a…198b
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