← previous blocknext block →recent activity

Analyzing

Block #90,067,686

15 transactions · 15 stateful · 2026-07-25 01:07:51 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.73

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,067,686  ·  15 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xee8237bd…46ad

0x34b655…2a6f

4 touches
1 conflict

0x3b56f79b…310f

0x34b655…2a6f

4 touches
1 conflict

0x3cb7ee74…b8a5

0x34b655…2a6f

4 touches
1 conflict

0xac3e4969…39e9

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 0xc824469a90…af6425

← previous block·next block →recent activity