← previous blocknext block →recent activity

Analyzing

Block #83,659,448

20 transactions · 16 stateful · 2026-06-25 19:02:55 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.8

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,659,448  ·  20 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

0x1306f7f4…8582

0xd32edf…ff58

7 touches
6 conflicts

0x7527802e…2ba9

0x34b655…2a6f

6 touches
3 conflicts

0x18904470…0ef9

0x34b655…2a6f

6 touches
3 conflicts

0xbd68c7c7…40b3

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c3

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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

6 conflicts on slot 0x1306f7f474…208582

← previous block·next block →recent activity