← previous blocknext block →recent activity

Analyzing

Block #99,275,776

18 transactions · 18 stateful · 2026-08-26 08:00:54 UTC

Parallelism

72/100

Blocked

39%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,275,776  ·  18 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x1aa72307…4260

0x34b655…2a6f

4 touches
1 conflict

0x48203298…65cb

0x34b655…2a6f

4 touches
1 conflict

0x5c1b956d…14d3

0x34b655…2a6f

4 touches
1 conflict

0x9d22c394…c125

0x34b655…2a6f

4 touches
1 conflict

0xd1b40f29…9b9d

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity