← previous blocknext block →recent activity

Analyzing

Block #104,203,508

21 transactions · 20 stateful · 2026-09-12 14:29:17 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #104,203,508  ·  21 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

0x6dedaff6…161b

0x34b655…2a6f

12 touches
15 conflicts

0xa46bcb14…455a

0x34b655…2a6f

8 touches
6 conflicts

0x425f4bff…057d

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0x21d8e673…067f

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

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: Perpl

15 conflicts on slot 0x6dedaff684…2d161b

← previous block·next block →recent activity