← previous blocknext block →recent activity

Analyzing

Block #105,844,409

21 transactions · 21 stateful · 2026-09-18 08:32:54 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #105,844,409  ·  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

0x5a548af5…0eb0

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xeebacabb…a34c

0x34b655…2a6f

12 touches
15 conflicts

0xc09c3422…3c8b

0x34b655…2a6f

8 touches
6 conflicts

0x0efc210e…70ab

0x34b655…2a6f

8 touches
6 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x7c216fca…20cb

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

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 0x5a548af508…f00eb0

← previous block·next block →recent activity