← previous blocknext block →recent activity

Analyzing

Block #106,164,388

25 transactions · 22 stateful · 2026-09-19 11:24:22 UTC

Parallelism

68/100

Blocked

41%

Avg conflicts / tx

1.48

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,164,388  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x51fc8795…126f

0x34b655…2a6f

12 touches
15 conflicts

0x7dd96c96…7335

0x34b655…2a6f

10 touches
10 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

10 touches
10 conflicts

0x58c1b78b…ef3f

0x34b655…2a6f

7 touches
6 conflicts

0xf18496c2…4f2f

0x34b655…2a6f

6 touches
3 conflicts

0x173b64af…6c43

0x34b655…2a6f

6 touches
3 conflicts

0x662d9b98…0f6b

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity