← previous blocknext block →recent activity

Analyzing

Block #90,630,270

13 transactions · 12 stateful · 2026-07-27 00:36:55 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,630,270  ·  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

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x1e56edff…5f5b

0x34b655…2a6f

6 touches
3 conflicts

0xb5a3b1be…8122

0x34b655…2a6f

4 touches
1 conflict

0xc7954a60…d294

0x34b655…2a6f

4 touches
1 conflict

0xe8d58d34…426d

0x34b655…2a6f

4 touches
1 conflict

0xebe581d8…2696

0x34b655…2a6f

4 touches
1 conflict

0x08e8f2c9…a11a

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

← previous block·next block →recent activity