← previous blocknext block →recent activity

Analyzing

Block #106,458,359

22 transactions · 21 stateful · 2026-09-20 12:03:56 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,458,359  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xb315b8e1…d6d4

0x34b655…2a6f

14 touches
21 conflicts

0x89eaf36a…4e48

0x34b655…2a6f

14 touches
21 conflicts

0x310a7246…2dcb

0x34b655…2a6f

8 touches
6 conflicts

0x6771eae2…7014

0x34b655…2a6f

8 touches
6 conflicts

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x1b25f260…c429

0x34b655…2a6f

4 touches
1 conflict

0x46483cb1…e7ca

0x34b655…2a6f

4 touches
1 conflict

0x49b9fdd5…9c16

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

21 conflicts on slot 0xb315b8e1d6…0dd6d4

← previous block·next block →recent activity