← previous blocknext block →recent activity

Analyzing

Block #104,192,599

21 transactions · 18 stateful · 2026-09-12 13:33:46 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #104,192,599  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x14084a98…58b3

0x34b655…2a6f

4 touches
1 conflict

0x45de70d9…e1dc

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x58edeb02…cfc5

0x34b655…2a6f

4 touches
1 conflict

0x5d6da397…6c5c

0x34b655…2a6f

4 touches
1 conflict

0x7d564c82…b3f1

0x34b655…2a6f

4 touches
1 conflict

0x7dd96c96…7335

0x34b655…2a6f

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

3 conflicts on slot 0xd66696e0dc…230842

← previous block·next block →recent activity