← previous blocknext block →recent activity

Analyzing

Block #86,390,404

39 transactions · 29 stateful · 2026-07-08 10:31:23 UTC

Parallelism

74/100

Blocked

59%

Avg conflicts / tx

1.44

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #86,390,404  ·  39 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x004b46ea…24ec

0xd32edf…ff58

19 touches
45 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x49cbdb1b…bda4

0x065c9d…c394

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0x1045386d…cb88

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

45 conflicts on slot 0x004b46ea60…0e24ec

← previous block·next block →recent activity