← previous blocknext block →recent activity
Analyzing
Block #99,210,034
33 transactions · 28 stateful · 2026-08-26 02:30:03 UTC
Parallelism
85/100
Blocked
57%
Avg conflicts / tx
0.97
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,210,034 · 33 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
1w02w13w26w07w110w011w115w117w020w321w022w123w224w225w326w327w328w430w131w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x38963aeb…c33f
0xa6afd3…d132
8 touches
6 conflicts
0x39773cec…38ed
0xa6afd3…d132
8 touches
6 conflicts
0xc2eefffc…b703
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd1480c90…ae07
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity