← previous blocknext block →recent activity

Analyzing

Block #90,784,720

16 transactions · 14 stateful · 2026-07-27 13:33:52 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,784,720  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xe8d58d34…426d

0x34b655…2a6f

6 touches
3 conflicts

0x40a6de3a…0973

0x34b655…2a6f

4 touches
1 conflict

0x4e58f1d6…2fca

0x34b655…2a6f

4 touches
1 conflict

0x502b3ee1…7f7b

0x34b655…2a6f

4 touches
1 conflict

0x53699236…fede

0x34b655…2a6f

4 touches
1 conflict

0x55f41b15…e3b5

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x803eb45d…00bd

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 0xe8d58d3462…c2426d

← previous block·next block →recent activity