← previous blocknext block →recent activity

Analyzing

Block #105,850,955

24 transactions · 20 stateful · 2026-09-18 09:05:52 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #105,850,955  ·  24 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

0x831f75b4…945d

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x3a6070ec…08c3

0x34b655…2a6f

8 touches
6 conflicts

0xdc9915b5…542c

0x34b655…2a6f

8 touches
6 conflicts

0x1d9867ad…6d9a

0x34b655…2a6f

8 touches
6 conflicts

0x4abfb389…18f4

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x6f5f06af…a612

0x34b655…2a6f

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

15 conflicts on slot 0x831f75b4aa…17945d

← previous block·next block →recent activity