← previous blocknext block →recent activity

Analyzing

Block #99,669,358

21 transactions · 20 stateful · 2026-08-27 17:09:26 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,669,358  ·  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

0x50807b43…b4ee

0x34b655…2a6f

6 touches
3 conflicts

0xe226a0be…c046

0x34b655…2a6f

6 touches
3 conflicts

0x4a45b318…9716

0x34b655…2a6f

6 touches
3 conflicts

0x0004b1fc…36b1

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2c1564ce…7fa8

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0x50807b43d0…68b4ee

← previous block·next block →recent activity