← previous blocknext block →recent activity

Analyzing

Block #98,275,226

22 transactions · 21 stateful · 2026-08-22 19:23:40 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,275,226  ·  22 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

0xfb0a4eb5…8be3

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x52cf5603…ca01

0x34b655…2a6f

6 touches
3 conflicts

0x793aa64d…b09c

0x34b655…2a6f

6 touches
3 conflicts

0x850f88e5…d8ce

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc0e3c294…f8ab

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641e

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

3 conflicts on slot 0xfb0a4eb5b0…018be3

← previous block·next block →recent activity