← previous blocknext block →recent activity

Analyzing

Block #106,481,597

23 transactions · 21 stateful · 2026-09-20 14:00:52 UTC

Parallelism

74/100

Blocked

33%

Avg conflicts / tx

1.09

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,481,597  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x34c3eea3…2b80

0x34b655…2a6f

8 touches
6 conflicts

0x397cbed5…f636

0x34b655…2a6f

8 touches
6 conflicts

0xdf64e5e6…75e8

0x34b655…2a6f

8 touches
6 conflicts

0x1c840894…764a

0x34b655…2a6f

8 touches
6 conflicts

0x5906754f…b584

0x34b655…2a6f

8 touches
6 conflicts

0x31d88d27…7617

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity