← previous blocknext block →recent activity

Analyzing

Block #81,102,226

22 transactions · 17 stateful · 2026-06-13 22:37:42 UTC

Parallelism

82/100

Blocked

41%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #81,102,226  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x1a07f774…8615

0xd32edf…ff58

7 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xfcb2447e…7571

0x065c9d…c394

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xe4af4c87…9964

0x34b655…2a6f

4 touches
1 conflict

0x25dbff47…47d1

0xa6afd3…d132

3 touches
1 conflict

0x864f5877…f52d

0x0594c7…a3be

2 touches
0 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

6 conflicts on slot 0x1a07f774e4…948615

← previous block·next block →recent activity