← previous blocknext block →recent activity

Analyzing

Block #106,932,851

22 transactions · 21 stateful · 2026-09-22 03:53:05 UTC

Parallelism

64/100

Blocked

67%

Avg conflicts / tx

1.59

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,932,851  ·  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

0xccebf5c5…8758

0x34b655…2a6f

10 touches
10 conflicts

0x0463db49…5d05

0x34b655…2a6f

10 touches
10 conflicts

0xf6deafb5…5c25

0x34b655…2a6f

10 touches
10 conflicts

0x643113d0…43d7

0x34b655…2a6f

10 touches
10 conflicts

0x6c26d635…1bbf

0x34b655…2a6f

10 touches
10 conflicts

0xba5743c7…21c4

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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

10 conflicts on slot 0xccebf5c5cb…c88758

← previous block·next block →recent activity