← previous blocknext block →recent activity

Analyzing

Block #98,384,730

20 transactions · 19 stateful · 2026-08-23 04:34:37 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,384,730  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x115183e2…1a53

0x34b655…2a6f

6 touches
3 conflicts

0x0afe5971…853e

0x34b655…2a6f

4 touches
1 conflict

0xfb4fd6ce…262e

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd192f4ed…d7ec

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity