← previous blocknext block →recent activity

Analyzing

Block #105,845,529

21 transactions · 19 stateful · 2026-09-18 08:38:34 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.19

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #105,845,529  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xa6d40b7f…2969

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x802ed271…71d3

0x34b655…2a6f

12 touches
15 conflicts

0x941bd594…21fd

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

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

21 conflicts on slot 0xa6d40b7f0d…ff2969

← previous block·next block →recent activity