← previous blocknext block →recent activity

Analyzing

Block #100,560,599

25 transactions · 20 stateful · 2026-08-30 20:05:29 UTC

Parallelism

68/100

Blocked

55%

Avg conflicts / tx

1.04

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #100,560,599  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x57bebc9e…2c5a

0xd32edf…ff58

13 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xea57afd0…4232

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

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 0x57bebc9e23…312c5a

← previous block·next block →recent activity