← previous blocknext block →recent activity

Analyzing

Block #106,539,789

24 transactions · 23 stateful · 2026-09-20 18:53:46 UTC

Parallelism

54/100

Blocked

48%

Avg conflicts / tx

1.67

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #106,539,789  ·  24 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

0x546fe1d2…eda3

0x34b655…2a6f

14 touches
21 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

10 touches
10 conflicts

0x1b25f260…c429

0x34b655…2a6f

10 touches
10 conflicts

0x9dd0a735…4d04

0x34b655…2a6f

10 touches
10 conflicts

0xecd87a39…d9c5

0x34b655…2a6f

8 touches
6 conflicts

0x524f0872…0d12

0x34b655…2a6f

8 touches
6 conflicts

0x6a925e11…2653

0x34b655…2a6f

8 touches
6 conflicts

0x71943d07…69fe

0x34b655…2a6f

8 touches
6 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 0x546fe1d2ed…d0eda3

← previous block·next block →recent activity