← previous blocknext block →recent activity

Analyzing

Block #98,729,938

26 transactions · 19 stateful · 2026-08-24 10:07:37 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,729,938  ·  26 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0dc33ff0…320b

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xd5ad0af4…2387

0x34b655…2a6f

6 touches
3 conflicts

0x60726f3c…b5b8

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

6 conflicts on slot 0xa02838a385…ffbc54

← previous block·next block →recent activity