← previous blocknext block →recent activity

Analyzing

Block #105,576,091

23 transactions · 20 stateful · 2026-09-17 10:00:59 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.74

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,576,091  ·  23 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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

8 touches
6 conflicts

0xfa805f95…72a4

0x34b655…2a6f

6 touches
3 conflicts

0x24d6bacf…5316

0x34b655…2a6f

6 touches
3 conflicts

0x32e1d03e…68a7

0x34b655…2a6f

6 touches
3 conflicts

0x7dbacbb4…9957

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0xc9ca92b3…ac3f

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

6 conflicts on slot 0x51fc8795c8…57126f

← previous block·next block →recent activity