← previous blocknext block →recent activity

Analyzing

Block #104,203,836

19 transactions · 19 stateful · 2026-09-12 14:30:58 UTC

Parallelism

53/100

Blocked

58%

Avg conflicts / tx

2.21

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #104,203,836  ·  19 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

14 touches
21 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0x6dedaff6…161b

0x34b655…2a6f

8 touches
6 conflicts

0x5c1fb664…cf50

0x34b655…2a6f

8 touches
6 conflicts

0x52343e15…a8de

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity