← previous blocknext block →recent activity

Analyzing

Block #99,329,199

16 transactions · 15 stateful · 2026-08-26 12:29:37 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.81

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,329,199  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf984d8ab…6e4f

0x34b655…2a6f

8 touches
6 conflicts

0x206c55db…94ea

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0xc813a46b…cc05

0x34b655…2a6f

6 touches
3 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

6 touches
3 conflicts

0x07b5c6c6…8868

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…00c9

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

6 conflicts on slot 0xf984d8ab41…c96e4f

← previous block·next block →recent activity