← previous blocknext block →recent activity

Analyzing

Block #106,281,610

21 transactions · 21 stateful · 2026-09-19 21:14:23 UTC

Parallelism

52/100

Blocked

62%

Avg conflicts / tx

1.57

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,281,610  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xe496f67d…65cf

0x34b655…2a6f

14 touches
21 conflicts

0x9ba10aad…9bc5

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x172b0de5…980b

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb80

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

21 conflicts on slot 0xe496f67da2…2165cf

← previous block·next block →recent activity