← previous blocknext block →recent activity

Analyzing

Block #95,371,210

18 transactions · 18 stateful · 2026-08-12 14:38:55 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,371,210  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x83f402f9…2c4c

0xd32edf…ff58

7 touches
6 conflicts

0x74137b07…5880

0x34b655…2a6f

6 touches
3 conflicts

0x673e2e56…9f5d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0x93afca4c…b47e

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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: FastLane: FastLaneAuctionHandler

6 conflicts on slot 0x83f402f93f…482c4c

← previous block·next block →recent activity