← previous blocknext block →recent activity

Analyzing

Block #98,206,859

19 transactions · 19 stateful · 2026-08-22 13:39:44 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,206,859  ·  19 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

0x41be9e75…9773

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x36a545a6…d40a

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x6fd9ae7c…e984

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

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

6 conflicts on slot 0x41be9e7517…b39773

← previous block·next block →recent activity