← previous blocknext block →recent activity

Analyzing

Block #105,857,767

19 transactions · 18 stateful · 2026-09-18 09:40:09 UTC

Parallelism

58/100

Blocked

56%

Avg conflicts / tx

1.16

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,857,767  ·  19 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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x8db32935…81a7

0x34b655…2a6f

12 touches
15 conflicts

0x8e68bd1f…e2a8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0xd996735f…872e

0x1b6862…e19c

6 touches
3 conflicts

0xb6ed511f…6b68

0x34b655…2a6f

6 touches
3 conflicts

0x1d9867ad…6d9a

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 0xc824469a90…af6425

← previous block·next block →recent activity