← previous blocknext block →recent activity

Analyzing

Block #105,583,249

24 transactions · 22 stateful · 2026-09-17 10:37:00 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,583,249  ·  24 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

0xb8bbc95f…5f39

0x34b655…2a6f

8 touches
6 conflicts

0xab41643c…f9bf

0x34b655…2a6f

6 touches
3 conflicts

0xca608d0c…f23b

0x34b655…2a6f

6 touches
3 conflicts

0xf5dc501b…8313

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

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 0xb8bbc95fb4…2d5f39

← previous block·next block →recent activity