← previous blocknext block →recent activity

Analyzing

Block #98,451,854

23 transactions · 21 stateful · 2026-08-23 10:12:20 UTC

Parallelism

87/100

Blocked

29%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,451,854  ·  23 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

0xd29e547b…a1dd

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eeb

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eec

0x34b655…2a6f

4 touches
1 conflict

0x9fc6ea79…e2dc

0x34b655…2a6f

4 touches
1 conflict

0xb1456a21…d57d

0x34b655…2a6f

4 touches
1 conflict

0xb3b620ed…64f4

0x34b655…2a6f

4 touches
1 conflict

0xb5f5f775…010b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xd29e547b5d…35a1dd

← previous block·next block →recent activity