← previous blocknext block →recent activity

Analyzing

Block #106,404,324

22 transactions · 22 stateful · 2026-09-20 07:31:56 UTC

Parallelism

50/100

Blocked

64%

Avg conflicts / tx

2.77

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #106,404,324  ·  22 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xba4adf08…3e3a

0x34b655…2a6f

16 touches
28 conflicts

0xfdd131fa…dbdb

0x34b655…2a6f

12 touches
15 conflicts

0xef948c34…0463

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x109d8a52…a7b7

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

28 conflicts on slot 0xba4adf0895…763e3a

← previous block·next block →recent activity