← previous blocknext block →recent activity

Analyzing

Block #98,025,329

25 transactions · 19 stateful · 2026-08-21 22:25:39 UTC

Parallelism

88/100

Blocked

32%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,025,329  ·  25 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

0xa759243a…e1ac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c2

0x1b6862…e19c

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

1 conflict on slot 0xa759243acd…e7e1ac

← previous block·next block →recent activity