← previous blocknext block →recent activity

Analyzing

Block #105,672,378

19 transactions · 19 stateful · 2026-09-17 18:05:42 UTC

Parallelism

58/100

Blocked

58%

Avg conflicts / tx

2.16

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,672,378  ·  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

0x86bd79a5…1f48

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x91c21110…90ce

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…001c

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…002c

0x1b6862…e19c

10 touches
10 conflicts

0xd4c913d7…343c

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x86bd79a5a6…961f48

← previous block·next block →recent activity