← previous blocknext block →recent activity

Analyzing

Block #106,956,564

23 transactions · 23 stateful · 2026-09-22 05:52:27 UTC

Parallelism

70/100

Blocked

65%

Avg conflicts / tx

2.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,956,564  ·  23 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

0x6598470a…6ad7

0x34b655…2a6f

14 touches
21 conflicts

0x772fc325…c0d8

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001e

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…002e

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0xea2d3331…6e37

0x1b6862…e19c

10 touches
10 conflicts

0x4786839b…c29a

0x34b655…2a6f

10 touches
10 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

21 conflicts on slot 0x6598470a71…b56ad7

← previous block·next block →recent activity