← previous blocknext block →recent activity

Analyzing

Block #106,907,251

20 transactions · 19 stateful · 2026-09-22 01:44:13 UTC

Parallelism

60/100

Blocked

58%

Avg conflicts / tx

1.65

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,907,251  ·  20 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

0x574628e9…dcc3

0x34b655…2a6f

16 touches
28 conflicts

0x42522e76…2592

0x34b655…2a6f

12 touches
15 conflicts

0x1e65a966…15e1

0x34b655…2a6f

12 touches
15 conflicts

0x7fc8f46e…0f75

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

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

28 conflicts on slot 0x574628e919…e4dcc3

← previous block·next block →recent activity