← previous blocknext block →recent activity

Analyzing

Block #104,206,503

17 transactions · 16 stateful · 2026-09-12 14:44:35 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #104,206,503  ·  17 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

0x1398e9f0…69ac

0x34b655…2a6f

8 touches
6 conflicts

0x3f64c80b…00b1

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x56a284d9…32e4

0x34b655…2a6f

8 touches
6 conflicts

0xa4e9800f…4ab0

0x34b655…2a6f

8 touches
6 conflicts

0xb9b077a8…e029

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…641e

0x34b655…2a6f

8 touches
6 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

6 conflicts on slot 0x1398e9f090…5569ac

← previous block·next block →recent activity