← previous blocknext block →recent activity

Analyzing

Block #90,807,609

30 transactions · 22 stateful · 2026-07-27 15:29:04 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.53

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,807,609  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

8 touches
6 conflicts

0x4c188934…158e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x26e32e90…8827

0x34b655…2a6f

4 touches
1 conflict

0x2981b6be…7be0

0x34b655…2a6f

4 touches
1 conflict

0x33967383…de4d

0x34b655…2a6f

4 touches
1 conflict

0x3eede796…d745

0x34b655…2a6f

4 touches
1 conflict

0x4f267385…cc89

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

← previous block·next block →recent activity