← previous blocknext block →recent activity
Analyzing
Block #86,763,254
16 transactions · 12 stateful · 2026-07-10 04:05:21 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,763,254 · 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
2w04w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4c35fcd…43ae
0xa6afd3…d132
4 touches
1 conflict
0xcc4a717b…efce
0x34b655…2a6f
4 touches
1 conflict
0xec7fe04a…3c56
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x46b62326…9b3c
0xa6afd3…d132
4 touches
1 conflict
0x89750670…2dea
0xa6afd3…d132
4 touches
1 conflict
0x0bc5d643…38d8
0x34b655…2a6f
4 touches
1 conflict
0x0bc5d643…38d9
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-WETH/USDC
1 conflict on slot 0xb4c35fcde1…0943ae
Audit this contract →
← previous block·next block →recent activity