← previous blocknext block →recent activity

Analyzing

Block #98,491,660

23 transactions · 22 stateful · 2026-08-23 13:32:57 UTC

Parallelism

70/100

Blocked

41%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,491,660  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x9d9f3717…44e7

0x34b655…2a6f

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xe48ab275…713e

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x261cbea7…e35e

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity