← previous blocknext block →recent activity

Analyzing

Block #99,113,525

21 transactions · 19 stateful · 2026-08-25 18:24:25 UTC

Parallelism

81/100

Blocked

32%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,113,525  ·  21 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

0x66e492f8…d95e

0x34b655…2a6f

8 touches
6 conflicts

0x810a3aa2…0227

0x34b655…2a6f

6 touches
3 conflicts

0xcc74f97b…ce51

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x83f3d320…fb59

0x34b655…2a6f

4 touches
1 conflict

0xa1731f0f…1f9d

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xf06fce24…887d

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 0x66e492f80d…04d95e

← previous block·next block →recent activity