← previous blocknext block →recent activity

Analyzing

Block #90,678,955

22 transactions · 20 stateful · 2026-07-27 04:41:50 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,678,955  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0x0a005879…de60

0x34b655…2a6f

6 touches
3 conflicts

0x80afd9d9…57cf

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x62dbeb4d…a388

0x34b655…2a6f

4 touches
1 conflict

0x70cfbacf…5c46

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity