← previous blocknext block →recent activity

Analyzing

Block #98,088,115

23 transactions · 22 stateful · 2026-08-22 03:41:36 UTC

Parallelism

57/100

Blocked

64%

Avg conflicts / tx

2.04

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #98,088,115  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xca841faa…486a

0x34b655…2a6f

18 touches
36 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

8 touches
6 conflicts

0x49299fcf…c552

0x34b655…2a6f

8 touches
6 conflicts

0x6d43ee99…bdd7

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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

36 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity