← previous blocknext block →recent activity

Analyzing

Block #106,551,099

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

Parallelism

64/100

Blocked

43%

Avg conflicts / tx

1.09

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,551,099  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xe1c4e5ce…0dec

0x34b655…2a6f

12 touches
15 conflicts

0xbc8fb280…76a3

0x34b655…2a6f

10 touches
10 conflicts

0x2b2f3976…1e6c

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb6

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x1032f16c…a9b1

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 0xe1c4e5ce15…770dec

← previous block·next block →recent activity