← previous blocknext block →recent activity

Analyzing

Block #106,569,403

20 transactions · 19 stateful · 2026-09-20 21:22:48 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,569,403  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc6615a36…3cf0

0x34b655…2a6f

12 touches
15 conflicts

0x4e0f8b54…e330

0x34b655…2a6f

8 touches
6 conflicts

0x5906754f…b584

0x34b655…2a6f

8 touches
6 conflicts

0x257ceaab…7a59

0x34b655…2a6f

8 touches
6 conflicts

0xac0b4a08…faae

0x34b655…2a6f

8 touches
6 conflicts

0x5a3732cb…edb2

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x1b25f260…c429

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

15 conflicts on slot 0xc6615a36ef…7f3cf0

← previous block·next block →recent activity