← previous blocknext block →recent activity

Analyzing

Block #90,803,273

24 transactions · 21 stateful · 2026-07-27 15:07:15 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,803,273  ·  24 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

0x0fd87a64…6651

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x41377979…0a18

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4f394483…ff62

0x34b655…2a6f

4 touches
1 conflict

0x53f393fa…00b9

0x34b655…2a6f

4 touches
1 conflict

0x610ed935…11c6

0x34b655…2a6f

4 touches
1 conflict

0x65487580…b5eb

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 0x0fd87a64db…786651

← previous block·next block →recent activity