← previous blocknext block →recent activity

Analyzing

Block #98,645,626

19 transactions · 18 stateful · 2026-08-24 02:54:07 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,645,626  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

12 touches
15 conflicts

0x886db264…846e

0x34b655…2a6f

11 touches
15 conflicts

0x1c645adf…cd53

0x34b655…2a6f

9 touches
10 conflicts

0xf98db8ee…a56d

0x34b655…2a6f

8 touches
6 conflicts

0x781a2c9b…f540

0x34b655…2a6f

6 touches
3 conflicts

0xdd23c3a7…53e4

0x34b655…2a6f

5 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

15 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity