← previous blocknext block →recent activity

Analyzing

Block #99,354,038

24 transactions · 20 stateful · 2026-08-26 14:34:37 UTC

Parallelism

88/100

Blocked

30%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,354,038  ·  24 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

0x00000000…0002

0xf5b5f7…6d70

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb26ff3de…9352

0xa6afd3…d132

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x89ac61bf…9443

0x34b655…2a6f

4 touches
1 conflict

0x00f7e3b7…e016

0x188d58…ea8e

2 touches
0 conflicts

0x889d5e90…929a

0x2a68ba…90c5

2 touches
0 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

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: 0xf5b5f7f8…a36d70

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity