← previous blocknext block →recent activity

Analyzing

Block #99,076,422

17 transactions · 15 stateful · 2026-08-25 15:17:25 UTC

Parallelism

88/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #99,076,422  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x9c6a9da2…c628

0x34b655…2a6f

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x43c7b92a…6042

0x065c9d…c394

3 touches
1 conflict

0xc5c4c1d1…2145

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0003

0x5e60bc…fe22

2 touches
0 conflicts

0x00000000…0004

0x5e60bc…fe22

2 touches
0 conflicts

0x00000000…0005

0x5e60bc…fe22

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 0x9c6a9da253…d0c628

← previous block·next block →recent activity