← previous blocknext block →recent activity

Analyzing

Block #71,045,302

23 transactions · 17 stateful · 2026-04-28 08:34:25 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,045,302  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x64b0afbe…39bf

0xd32edf…ff58

11 touches
15 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0x005fb969…2d97

0x34b655…2a6f

4 touches
1 conflict

0x04f0e47d…cb70

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x2d8c9ff9…8b1d

0x34b655…2a6f

4 touches
1 conflict

0x3254d19b…f714

0x34b655…2a6f

4 touches
1 conflict

0x3c35979a…975d

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

15 conflicts on slot 0x64b0afbe52…6d39bf

← previous block·next block →recent activity