← previous blocknext block →recent activity

Analyzing

Block #98,389,684

24 transactions · 24 stateful · 2026-08-23 04:59:32 UTC

Parallelism

63/100

Blocked

54%

Avg conflicts / tx

1.29

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #98,389,684  ·  24 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

10 touches
10 conflicts

0xc8d76375…d264

0xd32edf…ff58

9 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xb5c7c6aa…fdba

0x34b655…2a6f

8 touches
6 conflicts

0x8388993f…d18b

0x34b655…2a6f

7 touches
6 conflicts

0xba5743c7…21c1

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity