← previous blocknext block →recent activity

Analyzing

Block #99,987,897

16 transactions · 16 stateful · 2026-08-28 19:59:27 UTC

Parallelism

88/100

Blocked

19%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #99,987,897  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x05d5f037…360f

0x34b655…2a6f

4 touches
1 conflict

0x33649c4f…b327

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x51208b8d…9972

0x34b655…2a6f

4 touches
1 conflict

0x627738d1…db02

0x34b655…2a6f

4 touches
1 conflict

0x6b267bdf…b173

0x34b655…2a6f

4 touches
1 conflict

0x7b42f6a7…f49c

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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity