← previous blocknext block →recent activity

Analyzing

Block #104,320,915

13 transactions · 13 stateful · 2026-09-13 00:24:53 UTC

Parallelism

77/100

Blocked

15%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #104,320,915  ·  13 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

0x6728b7b2…71ae

0x34b655…2a6f

6 touches
3 conflicts

0xaf30c163…0fb6

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd66696e0…0842

0x34b655…2a6f

4 touches
1 conflict

0xea559e7b…41f4

0x34b655…2a6f

4 touches
1 conflict

0x759871b5…8eaa

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

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 0x6728b7b2ee…c271ae

← previous block·next block →recent activity