← previous blocknext block →recent activity

Analyzing

Block #98,756,026

27 transactions · 19 stateful · 2026-08-24 12:18:57 UTC

Parallelism

85/100

Blocked

37%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,756,026  ·  27 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x9c83a7b1…e305

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xd6d040d9…9ae3

0x34b655…2a6f

6 touches
3 conflicts

0x580c6fe7…0fe4

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x66ee9b39…e009

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 0x482471adbb…39122f

← previous block·next block →recent activity