← previous blocknext block →recent activity

Analyzing

Block #104,023,624

24 transactions · 20 stateful · 2026-09-11 23:14:37 UTC

Parallelism

79/100

Blocked

30%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #104,023,624  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x60d3cf20…db3f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x27034002…2f27

0x34b655…2a6f

6 touches
3 conflicts

0x8d1fba28…3e3f

0x065c9d…c394

4 touches
1 conflict

0x10379e8d…3675

0x34b655…2a6f

4 touches
1 conflict

0x1a3d2527…8ca0

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

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

6 conflicts on slot 0x60d3cf2090…5cdb3f

← previous block·next block →recent activity