← previous blocknext block →recent activity

Analyzing

Block #98,738,103

22 transactions · 20 stateful · 2026-08-24 10:48:41 UTC

Parallelism

82/100

Blocked

30%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,738,103  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xf984d8ab…6e4f

0x34b655…2a6f

4 touches
1 conflict

0x0ea82d2c…c412

0x34b655…2a6f

4 touches
1 conflict

0x152a2f3e…13f8

0x34b655…2a6f

4 touches
1 conflict

0x213ee207…a151

0x2b46c0…1669

2 touches
0 conflicts

0x2f74f175…9285

0x2b46c0…1669

2 touches
0 conflicts

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity