← previous blocknext block →recent activity

Analyzing

Block #102,413,636

24 transactions · 22 stateful · 2026-09-06 07:48:04 UTC

Parallelism

79/100

Blocked

36%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,413,636  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…641f

0x34b655…2a6f

10 touches
10 conflicts

0x56a284d9…32e4

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0xa4e9800f…4ab0

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641d

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…642d

0x34b655…2a6f

6 touches
3 conflicts

0x08cc68a2…2a59

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0xc824469a90…af641f

← previous block·next block →recent activity