← previous blocknext block →recent activity
Analyzing
Block #86,331,189
20 transactions · 19 stateful · 2026-07-08 03:55:43 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,331,189 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w112w213w314w415w417w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
10 touches
10 conflicts
0xddd20e39…d524
0x34b655…2a6f
6 touches
3 conflicts
0x8b9390da…3820
0x34b655…2a6f
6 touches
3 conflicts
0x3347cbe5…846c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc0c9700…ae04
0x34b655…2a6f
4 touches
1 conflict
0xe14e08ea…fd0b
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity