← previous blocknext block →recent activity

Analyzing

Block #83,944,407

29 transactions · 17 stateful · 2026-06-27 02:43:45 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

1.28

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,944,407  ·  29 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xef3b06f4…169b

0xd32edf…ff58

17 touches
36 conflicts

0x61d65579…ee3c

0xad96c3…8d7c

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xd821cffd…3ff0

0x754704…b603

4 touches
1 conflict

0x00000000…0008

0x86dbf0…eb2d

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x1c219bac…416e

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

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

36 conflicts on slot 0xef3b06f436…19169b

← previous block·next block →recent activity