← previous blocknext block →recent activity

Analyzing

Block #102,252,164

21 transactions · 20 stateful · 2026-09-05 18:09:57 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,252,164  ·  21 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

0xfa6b2636…e95c

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x7c93b38a…9e69

0x34b655…2a6f

6 touches
3 conflicts

0x4b024b98…8f37

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x894e445b…4b84

0x34b655…2a6f

4 touches
1 conflict

0x93f1d5e2…928f

0x34b655…2a6f

4 touches
1 conflict

0x93f1d5e2…9290

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 0xfa6b263629…5de95c

← previous block·next block →recent activity