← previous blocknext block →recent activity

Analyzing

Block #98,668,334

35 transactions · 28 stateful · 2026-08-24 04:52:34 UTC

Parallelism

71/100

Blocked

68%

Avg conflicts / tx

1.71

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #98,668,334  ·  35 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x54815843…f4c5

0xd32edf…ff58

11 touches
15 conflicts

0xe8f5e33f…719c

0x34b655…2a6f

9 touches
10 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21bf

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity