← previous blocknext block →recent activity

Analyzing

Block #104,321,706

21 transactions · 20 stateful · 2026-09-13 00:28:53 UTC

Parallelism

76/100

Blocked

35%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #104,321,706  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x45de70d9…e1dc

0x34b655…2a6f

6 touches
3 conflicts

0x48b13e5e…3c2a

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x74e1ffd8…9192

0x34b655…2a6f

4 touches
1 conflict

0x7c1fdb07…5e8d

0x34b655…2a6f

4 touches
1 conflict

0x8d32fccb…7cce

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity