← previous blocknext block →recent activity

Analyzing

Block #105,844,121

18 transactions · 17 stateful · 2026-09-18 08:31:27 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #105,844,121  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x844b7221…5ad8

0x34b655…2a6f

10 touches
10 conflicts

0x91424cd1…f433

0x34b655…2a6f

10 touches
10 conflicts

0xa6d40b7f…2969

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4d4389b2…6e07

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x5fad6fee…7714

0x34b655…2a6f

6 touches
3 conflicts

0xb75367ff…a2b7

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

10 conflicts on slot 0x844b7221ee…b65ad8

← previous block·next block →recent activity