← previous blocknext block →recent activity

Analyzing

Block #98,737,797

18 transactions · 16 stateful · 2026-08-24 10:47:09 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,737,797  ·  18 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

0xb64473b0…0d6f

0xc8689a…ee79

4 touches
1 conflict

0x7fcbd839…86af

0x34b655…2a6f

4 touches
1 conflict

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0xa60eabc0…9f8c

0x34b655…2a6f

4 touches
1 conflict

0xb240b520…a88a

0x34b655…2a6f

4 touches
1 conflict

0xb482658a…e4f5

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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: Settlement / Helper

1 conflict on slot 0xb64473b0af…bc0d6f

← previous block·next block →recent activity