← previous blocknext block →recent activity

Analyzing

Block #97,826,311

25 transactions · 23 stateful · 2026-08-21 05:31:10 UTC

Parallelism

80/100

Blocked

30%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,826,311  ·  25 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

8 touches
6 conflicts

0xcf10b6c3…c186

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2593

0x34b655…2a6f

4 touches
1 conflict

0x4be9812b…48a9

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…1266

0x34b655…2a6f

4 touches
1 conflict

0x60a536a6…ef7a

0x34b655…2a6f

4 touches
1 conflict

0x67cd7a5e…b25c

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