← previous blocknext block →recent activity

Analyzing

Block #90,602,968

7 transactions · 7 stateful · 2026-07-26 22:19:33 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,602,968  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe2be52ea…94be

0x34b655…2a6f

4 touches
1 conflict

0xed4a0d72…065f

0x34b655…2a6f

4 touches
1 conflict

0x5e03c37b…9df2

0x34b655…2a6f

4 touches
1 conflict

0x0725ad1d…a03f

0x34b655…2a6f

4 touches
1 conflict

0x934da4f1…43a7

0x34b655…2a6f

4 touches
1 conflict

0x8de38574…ad6e

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 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity