← previous blocknext block →recent activity

Analyzing

Block #104,202,736

26 transactions · 17 stateful · 2026-09-12 14:25:22 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #104,202,736  ·  26 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xe5bb3628…e5e8

0x34b655…2a6f

4 touches
1 conflict

0xfc2493d3…6898

0x34b655…2a6f

4 touches
1 conflict

0x10379e8d…3675

0x34b655…2a6f

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

2 touches
0 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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity