← previous blocknext block →recent activity

Analyzing

Block #106,801,377

22 transactions · 20 stateful · 2026-09-21 16:51:20 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,801,377  ·  22 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

0x6f5d7ccd…83d4

0x34b655…2a6f

10 touches
10 conflicts

0x5c0303fb…5285

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x38594928…2c55

0x34b655…2a6f

6 touches
3 conflicts

0x54f7f60f…43cc

0x34b655…2a6f

6 touches
3 conflicts

0x4abfb389…18f4

0x34b655…2a6f

6 touches
3 conflicts

0xe2c61c46…a216

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

10 conflicts on slot 0x6f5d7ccdbe…db83d4

← previous block·next block →recent activity