← previous blocknext block →recent activity

Analyzing

Block #99,111,747

19 transactions · 17 stateful · 2026-08-25 18:15:28 UTC

Parallelism

89/100

Blocked

12%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #99,111,747  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xabfdfd0e…20bf

0x34b655…2a6f

4 touches
1 conflict

0x3c9b10c1…d791

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0x6d5d1fb5…86a7

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x309f47c0…e1cf

0x34b655…2a6f

2 touches
0 conflicts

0x4f089e20…f71a

0x34b655…2a6f

2 touches
0 conflicts

0x5ad5e6de…e7ad

0x34b655…2a6f

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: Perpl

1 conflict on slot 0xabfdfd0ed9…6d20bf

← previous block·next block →recent activity