← previous blocknext block →recent activity

Analyzing

Block #102,564,584

24 transactions · 19 stateful · 2026-09-06 20:33:19 UTC

Parallelism

88/100

Blocked

37%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,564,584  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6ca15e14…7be8

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xe2d50773…c39e

0x34b655…2a6f

4 touches
1 conflict

0x2b42986e…5472

0x065c9d…c394

4 touches
1 conflict

0xfd4e632c…e14c

0x34b655…2a6f

4 touches
1 conflict

0xb8acd6db…8581

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

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

3 conflicts on slot 0x6ca15e14f4…917be8

← previous block·next block →recent activity