← previous blocknext block →recent activity

Analyzing

Block #98,261,346

21 transactions · 15 stateful · 2026-08-22 18:13:51 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,261,346  ·  21 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

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0xaf30c163…0fb6

0x34b655…2a6f

8 touches
6 conflicts

0xb5c7c6aa…fdba

0x34b655…2a6f

8 touches
6 conflicts

0xe3f37e64…31eb

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
3 conflicts

0x289ce6b2…d0ae

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

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 0xd66696e0dc…230842

← previous block·next block →recent activity