← previous blocknext block →recent activity

Analyzing

Block #105,626,044

23 transactions · 21 stateful · 2026-09-17 14:12:27 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,626,044  ·  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

0xba1edffb…323e

0x34b655…2a6f

8 touches
6 conflicts

0xf74e46c3…843d

0x34b655…2a6f

8 touches
6 conflicts

0xb2560305…f27d

0x34b655…2a6f

6 touches
3 conflicts

0xc09c3422…3c8b

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x5efbf797…b176

0x34b655…2a6f

4 touches
1 conflict

0x6964d687…fdcf

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 0xba1edffb42…64323e

← previous block·next block →recent activity