← previous blocknext block →recent activity

Analyzing

Block #90,070,289

21 transactions · 21 stateful · 2026-07-25 01:21:02 UTC

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,070,289  ·  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

0x94de4d05…ad01

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xf495a21d…99c7

0x34b655…2a6f

6 touches
3 conflicts

0xf7a558ca…e8e4

0x34b655…2a6f

6 touches
3 conflicts

0x2c2761c0…476e

0x34b655…2a6f

6 touches
3 conflicts

0x5e614061…7fbf

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

3 conflicts on slot 0x94de4d05c1…d4ad01

← previous block·next block →recent activity