← previous blocknext block →recent activity

Analyzing

Block #98,441,799

26 transactions · 19 stateful · 2026-08-23 09:21:44 UTC

Parallelism

77/100

Blocked

37%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,441,799  ·  26 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

0x6e66fa1f…1c87

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xe0904d40…1404

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xf06fce24…887d

0x34b655…2a6f

6 touches
3 conflicts

0x2105c873…2dee

0x34b655…2a6f

6 touches
3 conflicts

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0x6e66fa1fc8…251c87

← previous block·next block →recent activity