← previous blocknext block →recent activity

Analyzing

Block #105,852,400

21 transactions · 21 stateful · 2026-09-18 09:13:08 UTC

Parallelism

52/100

Blocked

52%

Avg conflicts / tx

1.76

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #105,852,400  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x89999c15…fdac

0x34b655…2a6f

10 touches
10 conflicts

0xe1540356…e970

0x34b655…2a6f

10 touches
10 conflicts

0x55192654…91fe

0x34b655…2a6f

10 touches
10 conflicts

0x00a49f64…8ad7

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0xef8f176a…ed6d

0x34b655…2a6f

8 touches
6 conflicts

0xa9988419…9f45

0x34b655…2a6f

8 touches
6 conflicts

0xb6ed511f…6b68

0x34b655…2a6f

8 touches
6 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

10 conflicts on slot 0x89999c1534…effdac

← previous block·next block →recent activity