← previous blocknext block →recent activity

Analyzing

Block #100,700,020

24 transactions · 21 stateful · 2026-08-31 07:46:48 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,700,020  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x66722c4d…8b4f

0xd32edf…ff58

7 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x51fc8795…1266

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xe44322e7…5829

0xa6afd3…d132

4 touches
1 conflict

0xd5b10148…e631

0x1b6862…e19c

2 touches
0 conflicts

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

6 conflicts on slot 0x66722c4d8f…078b4f

← previous block·next block →recent activity