← previous blocknext block →recent activity

Analyzing

Block #106,575,936

26 transactions · 25 stateful · 2026-09-20 21:55:40 UTC

Parallelism

77/100

Blocked

52%

Avg conflicts / tx

1.35

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,575,936  ·  26 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

0x94e7f277…471b

0x34b655…2a6f

10 touches
10 conflicts

0x1b25f260…c429

0x34b655…2a6f

8 touches
6 conflicts

0x317a8297…a8c6

0x34b655…2a6f

8 touches
6 conflicts

0x159cff26…7665

0x34b655…2a6f

8 touches
6 conflicts

0x3b6e959d…158f

0x34b655…2a6f

8 touches
6 conflicts

0x49b9fdd5…9c16

0x34b655…2a6f

8 touches
6 conflicts

0x8b827935…5a44

0x34b655…2a6f

8 touches
6 conflicts

0x941bd594…21fd

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

10 conflicts on slot 0x94e7f27794…c6471b

← previous block·next block →recent activity