← previous blocknext block →recent activity

Analyzing

Block #99,855,801

24 transactions · 19 stateful · 2026-08-28 08:53:44 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,855,801  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x15c6ded9…48e7

0x754704…b603

4 touches
1 conflict

0x5a7e4e98…1f3b

0x754704…b603

4 touches
1 conflict

0x8401a9f1…e868

0x754704…b603

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x45436af6…437f

0x99c7a7…8bf0

4 touches
1 conflict

0x66300207…c47a

0x99c7a7…8bf0

4 touches
1 conflict

0xf5dc501b…8313

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