← previous blocknext block →recent activity

Analyzing

Block #100,107,938

34 transactions · 23 stateful · 2026-08-29 06:03:45 UTC

Parallelism

79/100

Blocked

43%

Avg conflicts / tx

0.82

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,107,938  ·  34 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xa29aad71…0fce

0xd32edf…ff58

13 touches
21 conflicts

0x50c61506…343f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0xdb95e18e…c73c

0x1b6862…e19c

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

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

21 conflicts on slot 0xa29aad7128…620fce

← previous block·next block →recent activity