← previous blocknext block →recent activity

Analyzing

Block #102,138,387

13 transactions · 12 stateful · 2026-09-05 08:33:22 UTC

Parallelism

77/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,138,387  ·  13 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

0xdb8288e3…7979

0x34b655…2a6f

6 touches
3 conflicts

0x588380ee…0a5c

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd66696e0…0842

0x34b655…2a6f

4 touches
1 conflict

0xdc50859a…cabe

0x34b655…2a6f

4 touches
1 conflict

0xdc7b9eda…e616

0x34b655…2a6f

4 touches
1 conflict

0x502b3ee1…7f7c

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0xdb8288e38f…6f7979

← previous block·next block →recent activity