← previous blocknext block →recent activity

Analyzing

Block #99,669,355

22 transactions · 21 stateful · 2026-08-27 17:09:25 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0xdad20621…06b1

0x34b655…2a6f

8 touches
6 conflicts

0xcd9ba26b…108d

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xadd24be2…053d

0x34b655…2a6f

6 touches
3 conflicts

0xbaf77397…e798

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x2c1564ce…7fa8

0x34b655…2a6f

6 touches
3 conflicts

0x903069bd…d212

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

6 conflicts on slot 0xdad20621a2…0306b1

← previous block·next block →recent activity