← previous blocknext block →recent activity

Analyzing

Block #102,318,858

28 transactions · 17 stateful · 2026-09-05 23:47:54 UTC

Parallelism

79/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,318,858  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe1389bcb…c6e4

0xd32edf…ff58

11 touches
15 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

4 touches
1 conflict

0x06e40499…165e

0x34ae4d…3fc5

4 touches
1 conflict

0xb686e6f5…f6d1

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x77ed432f…fa04

0x065c9d…c394

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

15 conflicts on slot 0xe1389bcbaf…8cc6e4

← previous block·next block →recent activity