← previous blocknext block →recent activity

Analyzing

Block #99,253,618

22 transactions · 17 stateful · 2026-08-26 06:09:21 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,253,618  ·  22 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

0x46e2bb67…d8b3

0x34b655…2a6f

4 touches
1 conflict

0xb2d8af24…4750

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xb968a735…47f3

0xd32edf…ff58

3 touches
1 conflict

0xe75ce681…ba61

0x188d58…ea8e

2 touches
0 conflicts

0x3a921be0…779c

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