← previous blocknext block →recent activity
Analyzing
Block #86,764,335
19 transactions · 14 stateful · 2026-07-10 04:12:36 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,764,335 · 19 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
1w02w13w04w15w06w19w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46b62326…9b3c
0xa6afd3…d132
4 touches
1 conflict
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0x462c8be7…4f83
0xb1dbf0…c0d3
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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-WETH/USDC
1 conflict on slot 0x46b62326eb…ce9b3c
Audit this contract →
← previous block·next block →recent activity