← previous blocknext block →recent activity

Analyzing

Block #106,054,271

21 transactions · 20 stateful · 2026-09-19 02:10:11 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

1.14

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,054,271  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x886db264…846e

0x34b655…2a6f

8 touches
6 conflicts

0xfd3ea588…319c

0x34b655…2a6f

6 touches
3 conflicts

0x9ee73aa5…0d70

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5e8

0x34b655…2a6f

6 touches
3 conflicts

0xae969139…34b7

0x34b655…2a6f

5 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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity