← previous blocknext block →recent activity

Analyzing

Block #106,932,501

21 transactions · 20 stateful · 2026-09-22 03:51:19 UTC

Parallelism

57/100

Blocked

55%

Avg conflicts / tx

1.81

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #106,932,501  ·  21 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

0x858e40c0…7e30

0x34b655…2a6f

16 touches
28 conflicts

0xa088bd64…9bad

0x34b655…2a6f

10 touches
10 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

10 touches
10 conflicts

0x6c26d635…1bbf

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x51087f5a…61f7

0x34b655…2a6f

8 touches
6 conflicts

0xc3a899a7…a994

0x34b655…2a6f

8 touches
6 conflicts

0xe4bcafbe…10fc

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 0x858e40c022…9e7e30

← previous block·next block →recent activity