← previous blocknext block →recent activity

Analyzing

Block #98,071,030

21 transactions · 20 stateful · 2026-08-22 02:15:37 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

0.9

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #98,071,030  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xf15273a1…2c52

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…641e

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…641f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x523de645…4f58

0x34b655…2a6f

8 touches
6 conflicts

0x56a284d9…32e4

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

8 touches
6 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

6 conflicts on slot 0xf15273a148…932c52

← previous block·next block →recent activity