← previous blocknext block →recent activity

Analyzing

Block #100,729,214

28 transactions · 18 stateful · 2026-08-31 10:13:41 UTC

Parallelism

82/100

Blocked

50%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,729,214  ·  28 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

0x0327eb6f…3135

0xd32edf…ff58

9 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0x7048e456…4cb7

0x34b655…2a6f

4 touches
1 conflict

0x8311570f…5321

0x34b655…2a6f

4 touches
1 conflict

0xc10b903d…2f54

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 0x0327eb6fb2…413135

← previous block·next block →recent activity