← previous blocknext block →recent activity

Analyzing

Block #105,851,129

19 transactions · 18 stateful · 2026-09-18 09:06:45 UTC

Parallelism

37/100

Blocked

61%

Avg conflicts / tx

2.63

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #105,851,129  ·  19 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x548d7934…235a

0x34b655…2a6f

18 touches
36 conflicts

0xd6d040d9…9ae3

0x34b655…2a6f

16 touches
28 conflicts

0x4ade270b…14fb

0x34b655…2a6f

16 touches
28 conflicts

0x6caf33e2…c261

0x34b655…2a6f

14 touches
21 conflicts

0x932a9590…0b19

0x34b655…2a6f

12 touches
15 conflicts

0x89999c15…fdac

0x34b655…2a6f

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x42522e76…2592

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

36 conflicts on slot 0x548d793495…54235a

← previous block·next block →recent activity