← previous blocknext block →recent activity

Analyzing

Block #90,609,570

16 transactions · 15 stateful · 2026-07-26 22:52:46 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,609,570  ·  16 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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x3b1ce1dd…dc2f

0x34b655…2a6f

6 touches
3 conflicts

0x9365a4ed…946a

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xa1bfcc4c…f2db

0x851145…3f07

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity