← previous blocknext block →recent activity

Analyzing

Block #98,388,604

23 transactions · 20 stateful · 2026-08-23 04:54:06 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,388,604  ·  23 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

8 touches
6 conflicts

0x39e44cfd…c435

0x34b655…2a6f

8 touches
6 conflicts

0x678143da…dc6b

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x0a2131b3…455e

0x34b655…2a6f

4 touches
1 conflict

0x1e4337de…daef

0x34b655…2a6f

4 touches
1 conflict

0x3e6302c8…64f5

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity