← previous blocknext block →recent activity

Analyzing

Block #105,851,787

35 transactions · 35 stateful · 2026-09-18 09:10:03 UTC

Parallelism

71/100

Blocked

54%

Avg conflicts / tx

1.4

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #105,851,787  ·  35 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x831f75b4…945d

0x34b655…2a6f

14 touches
21 conflicts

0x25180879…8191

0x34b655…2a6f

8 touches
6 conflicts

0x2ed5ccb6…95d6

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x0efc210e…70ab

0x34b655…2a6f

8 touches
6 conflicts

0x52d2a8f9…c94f

0x34b655…2a6f

8 touches
6 conflicts

0x81ca8c9e…28cb

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0x831f75b4aa…17945d

← previous block·next block →recent activity