← previous blocknext block →recent activity

Analyzing

Block #82,274,031

27 transactions · 19 stateful · 2026-06-19 08:47:28 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #82,274,031  ·  27 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

0x3a2b6ab4…1e79

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0002

0x24b18e…3301

6 touches
3 conflicts

0xa743c8dd…ebf2

0x788571…8888

6 touches
3 conflicts

0x00000000…0000

0x24b18e…3301

6 touches
3 conflicts

0x771a3650…01cd

0x3bd359…433a

6 touches
3 conflicts

0x3bd55803…5d48

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x22e0cc1d…ad0d

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

10 conflicts on slot 0x3a2b6ab4c0…711e79

← previous block·next block →recent activity