← previous blocknext block →recent activity

Analyzing

Block #99,160,526

26 transactions · 20 stateful · 2026-08-25 22:20:59 UTC

Parallelism

88/100

Blocked

30%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,160,526  ·  26 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

0x33000c0a…82c3

0x34b655…2a6f

6 touches
3 conflicts

0x0ed7cc0b…ee52

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x833e1b6e…2f8f

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0xdc4713ad…9116

0x065c9d…c394

4 touches
1 conflict

0x248f83d1…63cf

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 0x33000c0a30…f582c3

← previous block·next block →recent activity