← previous blocknext block →recent activity

Analyzing

Block #106,802,098

21 transactions · 20 stateful · 2026-09-21 16:54:57 UTC

Parallelism

43/100

Blocked

60%

Avg conflicts / tx

1.67

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #106,802,098  ·  21 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x6d94f692…067a

0x34b655…2a6f

8 touches
6 conflicts

0x8704b69f…8bf8

0x34b655…2a6f

8 touches
6 conflicts

0x9edb7ad7…8d56

0x34b655…2a6f

8 touches
6 conflicts

0x1d9867ad…6d9a

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x6c26d635…1bbf

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

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 0xc824469a90…af6425

← previous block·next block →recent activity