← previous blocknext block →recent activity

Analyzing

Block #102,206,177

26 transactions · 25 stateful · 2026-09-05 14:17:02 UTC

Parallelism

88/100

Blocked

24%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,206,177  ·  26 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x113a6203…5dd8

0x34b655…2a6f

6 touches
3 conflicts

0x6823c28e…594c

0x34b655…2a6f

4 touches
1 conflict

0x7aa5d2c4…d6ef

0x34b655…2a6f

4 touches
1 conflict

0x897879a1…9c78

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

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 0xc824469a90…af6425

← previous block·next block →recent activity