← previous blocknext block →recent activity
Analyzing
Block #85,158,367
8 transactions · 8 stateful · 2026-07-02 17:37:17 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,158,367 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8210e2e5…29ca
0x065c9d…c394
4 touches
1 conflict
0x70c5d9da…9a02
0x065c9d…c394
3 touches
1 conflict
0x5ad10e4e…a75a
0x065c9d…c394
3 touches
1 conflict
0x7803622f…4995
0x065c9d…c394
2 touches
0 conflicts
0x7d98b15e…6af4
0x065c9d…c394
2 touches
0 conflicts
0xc892967e…228e
0x065c9d…c394
2 touches
0 conflicts
0xfedad958…a485
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