← previous blocknext block →recent activity

Analyzing

Block #98,380,658

28 transactions · 23 stateful · 2026-08-23 04:14:07 UTC

Parallelism

86/100

Blocked

26%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,380,658  ·  28 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xbb3f3c…e046

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x38c6ff01…689f

0x34b655…2a6f

4 touches
1 conflict

0x3c1123aa…4787

0x34b655…2a6f

4 touches
1 conflict

0x4f3a6b4a…3819

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