← previous blocknext block →recent activity

Analyzing

Block #98,736,608

19 transactions · 18 stateful · 2026-08-24 10:41:10 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,736,608  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x2d58efcf…af0b

0x34b655…2a6f

8 touches
6 conflicts

0xdc7b9eda…e616

0x34b655…2a6f

8 touches
6 conflicts

0x90a021f0…f922

0x34b655…2a6f

8 touches
6 conflicts

0x5778d110…d2e6

0xc8689a…ee79

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf51ec09c…b4a9

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity