← previous blocknext block →recent activity

Analyzing

Block #106,373,630

16 transactions · 16 stateful · 2026-09-20 04:57:28 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,373,630  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x5c8d8e93…e68a

0x34b655…2a6f

6 touches
3 conflicts

0xa5811d93…8c73

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x0262e1c6…52e1

0x34b655…2a6f

4 touches
1 conflict

0x4118bd12…924a

0x34b655…2a6f

4 touches
1 conflict

0x4d091c36…3028

0x34b655…2a6f

4 touches
1 conflict

0x72083f0d…082a

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 0xc824469a90…af6425

← previous block·next block →recent activity