← previous blocknext block →recent activity

Analyzing

Block #106,586,232

17 transactions · 17 stateful · 2026-09-20 22:47:30 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.88

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,586,232  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x1a24550d…aa05

0x34b655…2a6f

10 touches
10 conflicts

0xf9baf24c…c1fe

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xac0b4a08…faae

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xb9b077a8…e029

0x34b655…2a6f

4 touches
1 conflict

0x809f2ba8…89d3

0x34b655…2a6f

4 touches
1 conflict

0x1d9867ad…6d9a

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

10 conflicts on slot 0x1a24550deb…88aa05

← previous block·next block →recent activity