← previous blocknext block →recent activity

Analyzing

Block #98,269,984

21 transactions · 21 stateful · 2026-08-22 18:57:17 UTC

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,269,984  ·  21 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

0xe1c4e5ce…0dec

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xbd590df7…9891

0x34b655…2a6f

10 touches
10 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

10 touches
10 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

8 touches
6 conflicts

0xc4888af6…26b5

0x34b655…2a6f

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4ef969f4…86b4

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 0xe1c4e5ce15…770dec

← previous block·next block →recent activity