← previous blocknext block →recent activity

Analyzing

Block #98,984,676

17 transactions · 17 stateful · 2026-08-25 07:29:32 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,984,676  ·  17 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

0x261cbea7…e35d

0x34b655…2a6f

6 touches
3 conflicts

0x8692136a…16fc

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x261cbea7…e35e

0x34b655…2a6f

6 touches
3 conflicts

0x2aa4b9c6…42e7

0x34b655…2a6f

4 touches
1 conflict

0x3093e806…bde2

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

3 conflicts on slot 0x261cbea79d…12e35d

← previous block·next block →recent activity