← previous blocknext block →recent activity

Analyzing

Block #71,046,007

30 transactions · 22 stateful · 2026-04-28 08:39:07 UTC

Parallelism

73/100

Blocked

45%

Avg conflicts / tx

1.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,046,007  ·  30 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

0x1b96d388…b008

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x4bb71633…84f5

0x065c9d…c394

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

28 conflicts on slot 0x1b96d388ec…3ab008

← previous block·next block →recent activity