← previous blocknext block →recent activity
Analyzing
Block #86,232,623
29 transactions · 25 stateful · 2026-07-07 16:57:30 UTC
Parallelism
79/100
Blocked
56%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,232,623 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w17w110w111w012w115w016w217w320w121w322w423w524w326w027w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xbcdee322…f454
0xa6afd3…d132
10 touches
10 conflicts
0x17c44db3…8888
0xa6afd3…d132
8 touches
6 conflicts
0x05fdef9a…4e42
0xd32edf…ff58
7 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity