← previous blocknext block →recent activity

Analyzing

Block #99,710,005

17 transactions · 17 stateful · 2026-08-27 20:35:27 UTC

Parallelism

82/100

Blocked

18%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,710,005  ·  17 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

0xc799e56d…45aa

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x3e49348b…9445

0x34b655…2a6f

4 touches
1 conflict

0x454cdf57…aebc

0x34b655…2a6f

4 touches
1 conflict

0x213ee207…a151

0x2b46c0…1669

2 touches
0 conflicts

0x46279ae7…20dd

0x2b46c0…1669

2 touches
0 conflicts

0x53e50026…6d8c

0x2b46c0…1669

2 touches
0 conflicts

0x6eff310a…c34c

0x2b46c0…1669

2 touches
0 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

1 conflict on slot 0xc799e56dc0…c745aa

← previous block·next block →recent activity