← previous blocknext block →recent activity

Analyzing

Block #106,415,591

13 transactions · 12 stateful · 2026-09-20 08:28:38 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #106,415,591  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc2a722dc…1ef8

0x34b655…2a6f

4 touches
1 conflict

0xfd3d8226…d72f

0x34b655…2a6f

4 touches
1 conflict

0xfd3d8226…d730

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x3ea25e92…a36d

0x34b655…2a6f

4 touches
1 conflict

0x4265984a…a7d2

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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

1 conflict on slot 0xc2a722dcbd…9d1ef8

← previous block·next block →recent activity