← previous blocknext block →recent activity

Analyzing

Block #101,025,317

23 transactions · 18 stateful · 2026-09-01 11:03:40 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,025,317  ·  23 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x5ad17977…0e48

0xd32edf…ff58

9 touches
10 conflicts

0xf65c9ad4…88f7

0x34b655…2a6f

6 touches
3 conflicts

0x6b1259e6…4e14

0x1b6862…e19c

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xb75367ff…a2b7

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

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

10 conflicts on slot 0x5ad1797787…fc0e48

← previous block·next block →recent activity