← previous blocknext block →recent activity

Analyzing

Block #105,869,759

23 transactions · 23 stateful · 2026-09-18 10:40:30 UTC

Parallelism

61/100

Blocked

39%

Avg conflicts / tx

1.61

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #105,869,759  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x23529e13…6f25

0x34b655…2a6f

16 touches
28 conflicts

0x2fae69f2…54d5

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x329f9fde…fe9c

0x34b655…2a6f

8 touches
6 conflicts

0x6a344591…0c7a

0x34b655…2a6f

8 touches
6 conflicts

0x8063b7e8…32fd

0x34b655…2a6f

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

← previous block·next block →recent activity