← previous blocknext block →recent activity

Analyzing

Block #104,334,007

20 transactions · 17 stateful · 2026-09-13 01:31:19 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.3

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #104,334,007  ·  20 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

0x6d2969b2…662a

0xd32edf…ff58

13 touches
21 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x7759d2f5…f4b7

0x34b655…2a6f

4 touches
1 conflict

0xa7013be2…c0a8

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

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

21 conflicts on slot 0x6d2969b263…cc662a

← previous block·next block →recent activity