← previous blocknext block →recent activity

Analyzing

Block #84,360,484

54 transactions · 34 stateful · 2026-06-29 00:55:34 UTC

Parallelism

76/100

Blocked

71%

Avg conflicts / tx

1.76

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #84,360,484  ·  54 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xb9f046c1…0aef

0xd32edf…ff58

17 touches
36 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x1e346a85…e9c5

0x34b655…2a6f

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0x7c6984da…21e5

0x34b655…2a6f

8 touches
6 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

36 conflicts on slot 0xb9f046c1f7…df0aef

← previous block·next block →recent activity