← previous blocknext block →recent activity
Analyzing
Block #86,238,491
40 transactions · 31 stateful · 2026-07-07 17:36:40 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,238,491 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w412w013w116w017w120w123w225w229w530w631w732w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x823735e3…ec94
0xd32edf…ff58
9 touches
10 conflicts
0x006ee1d9…5485
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbcdee322…f454
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity