← previous blocknext block →recent activity

Analyzing

Block #102,477,374

22 transactions · 18 stateful · 2026-09-06 13:10:56 UTC

Parallelism

91/100

Blocked

28%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #102,477,374  ·  22 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x66b93c94…b337

0xd32edf…ff58

3 touches
1 conflict

0x46cb45de…a567

0x188d58…ea8e

2 touches
0 conflicts

0x0145aa28…106b

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x6ca15e14f4…917be8

← previous block·next block →recent activity