← previous blocknext block →recent activity

Analyzing

Block #85,855,738

27 transactions · 19 stateful · 2026-07-05 23:02:37 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,855,738  ·  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

0x5671eb83…d611

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…000a

0x90c374…be45

8 touches
6 conflicts

0x00000000…000b

0x90c374…be45

8 touches
6 conflicts

0x4a870d86…79ef

0x336ed4…c59c

6 touches
3 conflicts

0x47d4745e…02bb

0x336ed4…c59c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x7322fb4a…6358

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

10 conflicts on slot 0x5671eb8304…5bd611

← previous block·next block →recent activity