← previous blocknext block →recent activity
Analyzing
Block #85,125,036
16 transactions · 14 stateful · 2026-07-02 13:54:58 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,125,036 · 16 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
1w02w05w08w19w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b3114cd…5e2d
0xa6afd3…d132
4 touches
1 conflict
0x22d3c767…e4d1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x63da0619…7a55
0x34b655…2a6f
4 touches
1 conflict
0x66c5e348…51d0
0xa6afd3…d132
4 touches
1 conflict
0x3559fd36…df81
0xa6afd3…d132
3 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
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-WETH/USDC
1 conflict on slot 0x1b3114cdec…355e2d
Audit this contract →
← previous block·next block →recent activity