← previous blocknext block →recent activity

Analyzing

Block #98,378,422

20 transactions · 18 stateful · 2026-08-23 04:02:53 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,378,422  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xcaa5e459…c7eb

0x34b655…2a6f

6 touches
3 conflicts

0xa923f975…c1d3

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x3c6c2e62…6fcd

0x34b655…2a6f

4 touches
1 conflict

0x4c20d376…0819

0x34b655…2a6f

4 touches
1 conflict

0x5e47cbde…9659

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 0xac2a02739b…81721b

← previous block·next block →recent activity