← previous blocknext block →recent activity

Analyzing

Block #99,987,815

51 transactions · 48 stateful · 2026-08-28 19:59:02 UTC

Parallelism

90/100

Blocked

15%

Avg conflicts / tx

0.18

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,987,815  ·  51 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x36126dcb…ca1e

0x34b655…2a6f

4 touches
1 conflict

0x461661b9…f714

0x34b655…2a6f

4 touches
1 conflict

0x5273be82…485e

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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 0xc824469a90…af6425

← previous block·next block →recent activity