← previous blocknext block →recent activity

Analyzing

Block #90,604,634

17 transactions · 10 stateful · 2026-07-26 22:27:56 UTC

Parallelism

76/100

Blocked

30%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,604,634  ·  17 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

0xf2f4727d…cdb7

0x34b655…2a6f

6 touches
3 conflicts

0x48e3acd8…cf41

0x34b655…2a6f

4 touches
1 conflict

0x4f3a6b4a…3819

0x34b655…2a6f

4 touches
1 conflict

0x6cfabf20…d256

0x34b655…2a6f

4 touches
1 conflict

0x6e56bfba…e883

0x34b655…2a6f

4 touches
1 conflict

0x6f1a10f8…5a04

0x34b655…2a6f

4 touches
1 conflict

0x7a9a468f…e378

0x34b655…2a6f

4 touches
1 conflict

0x8e9a7d26…688c

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 0xf2f4727df6…a5cdb7

← previous block·next block →recent activity