← previous blocknext block →recent activity

Analyzing

Block #106,943,809

22 transactions · 21 stateful · 2026-09-22 04:48:14 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

1.27

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,943,809  ·  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

0x85c5ea16…1194

0x34b655…2a6f

14 touches
21 conflicts

0xd125c3f8…99aa

0x34b655…2a6f

8 touches
6 conflicts

0x6c26d635…1bbf

0x34b655…2a6f

8 touches
6 conflicts

0x810a3aa2…0227

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x1785cf5f…58ba

0x34b655…2a6f

6 touches
3 conflicts

0x4e58deff…c5d0

0x34b655…2a6f

6 touches
3 conflicts

0x49b9fdd5…9c16

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

21 conflicts on slot 0x85c5ea1650…831194

← previous block·next block →recent activity