← previous blocknext block →recent activity
Analyzing
Block #99,475,543
11 transactions · 11 stateful · 2026-08-27 00:46:34 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,475,543 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5b09bf44…5907
0xa6afd3…d132
4 touches
1 conflict
0x6d8ad688…4bf5
0xa6afd3…d132
4 touches
1 conflict
0x3c34bb20…8d72
0x34b655…2a6f
2 touches
0 conflicts
0x3e49348b…9445
0x34b655…2a6f
2 touches
0 conflicts
0x450f5a60…bf64
0x34b655…2a6f
2 touches
0 conflicts
0x68c740e2…58d6
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity