← previous blocknext block →recent activity

Analyzing

Block #98,067,224

18 transactions · 16 stateful · 2026-08-22 01:56:28 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,067,224  ·  18 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

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x5c1b956d…14d3

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x8324541f…7500

0x34b655…2a6f

4 touches
1 conflict

0x9ae859db…2d84

0x34b655…2a6f

4 touches
1 conflict

0xd1899d1a…63fc

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

← previous block·next block →recent activity