← previous blocknext block →recent activity

Analyzing

Block #98,499,622

23 transactions · 19 stateful · 2026-08-23 14:13:09 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,499,622  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0xb5cddf91…0abf

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x076e4b80…4d01

0x34b655…2a6f

5 touches
3 conflicts

0xa9a36554…c73a

0x34b655…2a6f

4 touches
1 conflict

0x39773cec…38ed

0xa6afd3…d132

4 touches
1 conflict

0x398e1fec…f13e

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity