← previous blocknext block →recent activity

Analyzing

Block #90,067,690

13 transactions · 13 stateful · 2026-07-25 01:07:52 UTC

Parallelism

69/100

Blocked

46%

Avg conflicts / tx

0.77

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,067,690  ·  13 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

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xac3e4969…39e9

0x34b655…2a6f

6 touches
3 conflicts

0x0c57679c…99c9

0x34b655…2a6f

4 touches
1 conflict

0x0d488000…3831

0x34b655…2a6f

4 touches
1 conflict

0x146dc18d…d0ac

0x34b655…2a6f

4 touches
1 conflict

0xc5a847e4…8333

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

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

← previous block·next block →recent activity