← previous blocknext block →recent activity

Analyzing

Block #106,476,529

18 transactions · 18 stateful · 2026-09-20 13:35:23 UTC

Parallelism

72/100

Blocked

39%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,476,529  ·  18 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

0xf6d2da5f…9e78

0x34b655…2a6f

8 touches
6 conflicts

0xf77fbd5a…8833

0x34b655…2a6f

8 touches
6 conflicts

0xfcc8f826…7c5f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x91ecc547…33ef

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x1cdfe548…d3aa

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 0xf6d2da5f70…b69e78

← previous block·next block →recent activity