← previous blocknext block →recent activity

Analyzing

Block #105,377,771

25 transactions · 24 stateful · 2026-09-16 17:22:47 UTC

Parallelism

60/100

Blocked

63%

Avg conflicts / tx

1.52

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #105,377,771  ·  25 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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0x100812e9…12b7

0x34b655…2a6f

10 touches
10 conflicts

0x284f8c8e…02d2

0x34b655…2a6f

8 touches
6 conflicts

0x48b6f2c7…2ef7

0x34b655…2a6f

8 touches
6 conflicts

0x4a45b318…9716

0x34b655…2a6f

8 touches
6 conflicts

0x4c572488…35d9

0x34b655…2a6f

8 touches
6 conflicts

0x4cff6b80…47a8

0x34b655…2a6f

8 touches
6 conflicts

0x4f04c0ac…3f3b

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 0xca841faae5…71486a

← previous block·next block →recent activity