← previous blocknext block →recent activity

Analyzing

Block #94,750,756

43 transactions · 32 stateful · 2026-08-10 10:25:00 UTC

Parallelism

72/100

Blocked

63%

Avg conflicts / tx

1.88

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #94,750,756  ·  43 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xabe1c163…e7a1

0xd32edf…ff58

23 touches
66 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x3439dfbc…0d03

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x93afca4c…b479

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

66 conflicts on slot 0xabe1c16335…fde7a1

← previous block·next block →recent activity