← previous blocknext block →recent activity
Analyzing
Block #85,145,675
25 transactions · 20 stateful · 2026-07-02 16:12:45 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,145,675 · 25 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
1w03w08w010w111w213w014w116w119w123w124w2
- 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
0x187d3a31…8565
0x34b655…2a6f
4 touches
1 conflict
0x1e7e4246…4872
0x34b655…2a6f
4 touches
1 conflict
0x2549dda6…9e24
0x34b655…2a6f
4 touches
1 conflict
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0x3fde350e…8d43
0x34b655…2a6f
4 touches
1 conflict
0x52245372…ad6b
0x34b655…2a6f
4 touches
1 conflict
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