← previous blocknext block →recent activity

Analyzing

Block #105,366,503

21 transactions · 19 stateful · 2026-09-16 16:26:06 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,366,503  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x0a8f8b9c…3046

0x34b655…2a6f

6 touches
3 conflicts

0x126c10ea…a328

0x34b655…2a6f

6 touches
3 conflicts

0x2b5101ac…090b

0x34b655…2a6f

6 touches
3 conflicts

0x5164ab0e…01e1

0xc8689a…ee79

6 touches
3 conflicts

0xc08384da…ecb7

0x34b655…2a6f

6 touches
3 conflicts

0xd24f93ae…3667

0x34b655…2a6f

6 touches
3 conflicts

0x2a8bc05a…0464

0x37db7f…ec7b

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity