← previous blocknext block →recent activity

Analyzing

Block #99,935,612

28 transactions · 25 stateful · 2026-08-28 15:35:59 UTC

Parallelism

82/100

Blocked

28%

Avg conflicts / tx

0.36

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,935,612  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x2130a548…c1de

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc1c06198…2b57

0x851145…3f07

4 touches
1 conflict

0x172b0de5…980b

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x126b93b9…b8f7

0x851145…3f07

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 0x2130a548b9…31c1de

← previous block·next block →recent activity