← previous blocknext block →recent activity
Analyzing
Block #86,238,461
24 transactions · 17 stateful · 2026-07-07 17:36:28 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,238,461 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w013w117w220w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xbcdee322…f454
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x006ee1d9…5485
0xa6afd3…d132
6 touches
3 conflicts
0xd535e053…91fa
0x34b655…2a6f
4 touches
1 conflict
0x614515d2…e871
0x34b655…2a6f
4 touches
1 conflict
0xf94a1720…de9e
0xa6afd3…d132
3 touches
1 conflict
0x03a406d8…b4ac
0xa6afd3…d132
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity