← previous blocknext block →recent activity

Analyzing

Block #102,484,787

30 transactions · 19 stateful · 2026-09-06 13:48:33 UTC

Parallelism

87/100

Blocked

32%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,484,787  ·  30 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x222f58e2…1089

0xd32edf…ff58

7 touches
6 conflicts

0x082a85db…aade

0x34b655…2a6f

4 touches
1 conflict

0x33761f7c…8f85

0x34b655…2a6f

4 touches
1 conflict

0x61ca7e1c…6d7b

0x34b655…2a6f

4 touches
1 conflict

0xdf146090…28f8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0002

0xf5b5f7…6d70

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

6 conflicts on slot 0x222f58e26a…431089

← previous block·next block →recent activity