← previous blocknext block →recent activity

Analyzing

Block #98,072,279

23 transactions · 21 stateful · 2026-08-22 02:21:54 UTC

Parallelism

74/100

Blocked

33%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,072,279  ·  23 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x9e1c65d0…77a3

0x34b655…2a6f

6 touches
3 conflicts

0xc6ff19c6…5250

0x34b655…2a6f

6 touches
3 conflicts

0x9ae859db…2d84

0x34b655…2a6f

6 touches
3 conflicts

0xd8834cf3…0004

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xffdabeff…d6aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0x340143…768f

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity