← previous blocknext block →recent activity

Analyzing

Block #98,502,029

25 transactions · 24 stateful · 2026-08-23 14:25:42 UTC

Parallelism

48/100

Blocked

58%

Avg conflicts / tx

1.52

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #98,502,029  ·  25 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x9d9f3717…44e7

0x34b655…2a6f

6 touches
3 conflicts

0xbaf77397…e798

0x34b655…2a6f

6 touches
3 conflicts

0x4b544c60…d984

0x34b655…2a6f

6 touches
3 conflicts

0x0e18d182…0425

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

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

15 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity