← previous blocknext block →recent activity

Analyzing

Block #98,059,243

22 transactions · 17 stateful · 2026-08-22 01:16:18 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,059,243  ·  22 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

0xe9810e69…aa0e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2bd1c200…56de

0x34b655…2a6f

4 touches
1 conflict

0x9c83a7b1…e305

0x34b655…2a6f

4 touches
1 conflict

0x9fc6ea79…e2dc

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xcf71e9af…aaad

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

1 conflict on slot 0xe9810e69d2…ffaa0e

← previous block·next block →recent activity