← previous blocknext block →recent activity

Analyzing

Block #99,287,768

24 transactions · 20 stateful · 2026-08-26 09:01:13 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.71

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,287,768  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x300807d1…7aa5

0x34b655…2a6f

6 touches
3 conflicts

0xfe65bb7b…12d7

0x34b655…2a6f

6 touches
3 conflicts

0x3d93ad2c…e747

0x34b655…2a6f

4 touches
1 conflict

0x42e5184f…4e8b

0x34b655…2a6f

4 touches
1 conflict

0x8b7fe709…9d99

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity