← previous blocknext block →recent activity

Analyzing

Block #106,163,981

27 transactions · 23 stateful · 2026-09-19 11:22:19 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

1.48

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,163,981  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xad997964…99d9

0x34b655…2a6f

16 touches
28 conflicts

0x941bd594…21fd

0x34b655…2a6f

10 touches
10 conflicts

0xe098738f…9bbe

0x34b655…2a6f

10 touches
10 conflicts

0xb550abea…2729

0x34b655…2a6f

10 touches
10 conflicts

0x51f1f20c…d9da

0x34b655…2a6f

8 touches
6 conflicts

0x1b25f260…c429

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0x949f6fc3…c2ae

0x34b655…2a6f

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

28 conflicts on slot 0xad997964d9…6299d9

← previous block·next block →recent activity