← previous blocknext block →recent activity

Analyzing

Block #90,602,751

22 transactions · 18 stateful · 2026-07-26 22:18:27 UTC

Parallelism

55/100

Blocked

61%

Avg conflicts / tx

1.32

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #90,602,751  ·  22 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

12 touches
15 conflicts

0x48e3acd8…cf41

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x217bd767…b79e

0x34b655…2a6f

6 touches
3 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0x6f28eb14…e5ef

0x34b655…2a6f

4 touches
1 conflict

0x7103aaf4…ddc5

0x34b655…2a6f

4 touches
1 conflict

0xbe54b7d5…1bda

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity