← previous blocknext block →recent activity

Analyzing

Block #102,655,393

22 transactions · 21 stateful · 2026-09-07 04:12:23 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,655,393  ·  22 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

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xf5b5f7…6d70

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

6 touches
3 conflicts

0xb3572c95…9c4a

0x2a68ba…90c5

4 touches
1 conflict

0x7dd96c96…7335

0x34b655…2a6f

4 touches
1 conflict

0x5b09bf44…5907

0xa6afd3…d132

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 0x51fc8795c8…57126f

← previous block·next block →recent activity