← previous blocknext block →recent activity

Analyzing

Block #98,420,676

18 transactions · 17 stateful · 2026-08-23 07:35:28 UTC

Parallelism

72/100

Blocked

41%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,420,676  ·  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

0xcdd556aa…31d0

0x34b655…2a6f

6 touches
3 conflicts

0xf47b941b…b814

0xa6afd3…d132

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xda976e7f…128a

0x34b655…2a6f

4 touches
1 conflict

0xf3b253be…78b5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x3e598447…0e3f

0xa6afd3…d132

4 touches
1 conflict

0x22e0cc1d…ad0d

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 0xcdd556aab1…2c31d0

← previous block·next block →recent activity