← previous blocknext block →recent activity

Analyzing

Block #105,868,850

24 transactions · 21 stateful · 2026-09-18 10:35:56 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,868,850  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x47c42e8a…180a

0x34b655…2a6f

8 touches
6 conflicts

0x6caf33e2…c261

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xb5c7c6aa…fdba

0x34b655…2a6f

6 touches
3 conflicts

0x18978822…2623

0x34b655…2a6f

6 touches
3 conflicts

0x2f0f281c…9e72

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x42522e76…2592

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

6 conflicts on slot 0x47c42e8ab2…a9180a

← previous block·next block →recent activity