← previous blocknext block →recent activity

Analyzing

Block #106,215,298

23 transactions · 20 stateful · 2026-09-19 15:40:37 UTC

Parallelism

78/100

Blocked

30%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,215,298  ·  23 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x1b25f260…c429

0x34b655…2a6f

10 touches
10 conflicts

0xf00e711b…c539

0x34b655…2a6f

8 touches
6 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

6 touches
3 conflicts

0x065566a3…cf1b

0x34b655…2a6f

6 touches
3 conflicts

0x12503a94…ffdb

0x34b655…2a6f

6 touches
3 conflicts

0x1afc902d…3ee1

0x34b655…2a6f

6 touches
3 conflicts

0x3fa1fac4…826c

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity