← previous blocknext block →recent activity

Analyzing

Block #98,661,367

18 transactions · 17 stateful · 2026-08-24 04:16:20 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,661,367  ·  18 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

0xd97b0449…00a0

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x1456f7c9…ca2d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x8d47c9a4…f11a

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x855bb14e…792c

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

3 conflicts on slot 0xd97b04496e…0c00a0

← previous block·next block →recent activity