← previous blocknext block →recent activity

Analyzing

Block #99,331,179

16 transactions · 15 stateful · 2026-08-26 12:39:35 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.75

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,331,179  ·  16 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

0xf06fce24…887d

0x34b655…2a6f

6 touches
3 conflicts

0x5b6af007…0f35

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x23529e13…6f25

0x34b655…2a6f

4 touches
1 conflict

0x2fae69f2…54d5

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3e49348b…9445

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

3 conflicts on slot 0xf06fce24b3…55887d

← previous block·next block →recent activity