← previous blocknext block →recent activity

Analyzing

Block #99,811,265

20 transactions · 16 stateful · 2026-08-28 05:08:34 UTC

Parallelism

85/100

Blocked

38%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,811,265  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb4c703ab…f8cf

0x34b655…2a6f

6 touches
3 conflicts

0x34c2d69b…3753

0x8964d7…10f8

4 touches
1 conflict

0x00000000…0008

0x8964d7…10f8

4 touches
1 conflict

0x34c2d69b…374e

0x8964d7…10f8

4 touches
1 conflict

0x34c2d69b…374f

0x8964d7…10f8

4 touches
1 conflict

0x34c2d69b…3752

0x8964d7…10f8

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x69411fb3…e36d

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 0xb4c703ab76…fdf8cf

← previous block·next block →recent activity