← previous blocknext block →recent activity

Analyzing

Block #99,200,324

21 transactions · 20 stateful · 2026-08-26 01:41:13 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,200,324  ·  21 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

0x8b98c194…d69e

0x851145…3f07

4 touches
1 conflict

0xe04c5c51…c043

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x2274142b…f885

0x851145…3f07

4 touches
1 conflict

0x7188d03a…1728

0x851145…3f07

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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: 0x851145ea…9f3f07

1 conflict on slot 0x8b98c1949c…27d69e

← previous block·next block →recent activity