← previous blocknext block →recent activity

Analyzing

Block #98,604,510

20 transactions · 19 stateful · 2026-08-23 23:20:12 UTC

Parallelism

60/100

Blocked

47%

Avg conflicts / tx

0.9

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #98,604,510  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x627738d1…db02

0x34b655…2a6f

8 touches
6 conflicts

0xfc1d1594…b59f

0x34b655…2a6f

8 touches
6 conflicts

0x0505bae8…b4fb

0x34b655…2a6f

8 touches
6 conflicts

0xa9988419…9f45

0x34b655…2a6f

6 touches
3 conflicts

0x514a514b…93d7

0x34b655…2a6f

6 touches
3 conflicts

0xb9b077a8…e029

0x34b655…2a6f

4 touches
1 conflict

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 0xc824469a90…af6425

← previous block·next block →recent activity