← previous blocknext block →recent activity

Analyzing

Block #99,503,373

21 transactions · 21 stateful · 2026-08-27 03:06:43 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,503,373  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x9a100e05…c541

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xf0aa564c…8d2f

0x34b655…2a6f

8 touches
6 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

8 touches
6 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

8 touches
6 conflicts

0x70d81211…f49f

0x34b655…2a6f

6 touches
3 conflicts

0xb1856468…e84f

0x34b655…2a6f

6 touches
3 conflicts

0x574628e9…dcc3

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0x9a100e057a…2ac541

← previous block·next block →recent activity