← previous blocknext block →recent activity

Analyzing

Block #98,066,626

26 transactions · 22 stateful · 2026-08-22 01:53:27 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,066,626  ·  26 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

0x49299fcf…c552

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x0c5dc9f7…3729

0x34b655…2a6f

4 touches
1 conflict

0x17ff2059…ddb4

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 0x49299fcf8b…f1c552

← previous block·next block →recent activity