← previous blocknext block →recent activity

Analyzing

Block #98,651,749

26 transactions · 24 stateful · 2026-08-24 03:26:01 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,651,749  ·  26 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

0xf98db8ee…a56d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5d6da397…6c5c

0x34b655…2a6f

6 touches
3 conflicts

0xa02838a3…bc54

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eeb

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eec

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 0xf98db8ee72…13a56d

← previous block·next block →recent activity