← previous blocknext block →recent activity

Analyzing

Block #106,931,247

30 transactions · 28 stateful · 2026-09-22 03:45:01 UTC

Parallelism

83/100

Blocked

21%

Avg conflicts / tx

0.33

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,931,247  ·  30 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd125c3f8…99aa

0x34b655…2a6f

6 touches
3 conflicts

0xd1524132…52f1

0x34b655…2a6f

6 touches
3 conflicts

0xbc93cdd5…5bf5

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

3 conflicts on slot 0xd125c3f898…5599aa

← previous block·next block →recent activity