← previous blocknext block →recent activity

Analyzing

Block #86,182,878

27 transactions · 25 stateful · 2026-07-07 11:25:15 UTC

Parallelism

70/100

Blocked

52%

Avg conflicts / tx

1.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,182,878  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x7ad5983a…5886

0xd32edf…ff58

13 touches
21 conflicts

0x18cf3003…51d1

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x7d42dc8b…fdb6

0x2a68ba…90c5

6 touches
3 conflicts

0xcc8faac2…c766

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

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

21 conflicts on slot 0x7ad5983a22…9c5886

← previous block·next block →recent activity