← previous blocknext block →recent activity

Analyzing

Block #106,425,871

18 transactions · 16 stateful · 2026-09-20 09:20:22 UTC

Parallelism

56/100

Blocked

63%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,425,871  ·  18 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

0xe687084c…5c03

0x34b655…2a6f

12 touches
15 conflicts

0x38bcfe5f…6c71

0x34b655…2a6f

8 touches
6 conflicts

0xb0e974c4…b84d

0x34b655…2a6f

8 touches
6 conflicts

0x9a6c063c…a1e3

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x14d1bf0e…e09c

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0ed7cc0b…ee52

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

15 conflicts on slot 0xe687084c07…a05c03

← previous block·next block →recent activity