← previous blocknext block →recent activity

Analyzing

Block #89,580,781

18 transactions · 15 stateful · 2026-07-23 06:07:44 UTC

Parallelism

83/100

Blocked

20%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,580,781  ·  18 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

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0x4f1ad4b4…e00a

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x72880226…1435

0x34b655…2a6f

4 touches
1 conflict

0x808ff8b4…4450

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x24b6091e…d294

0x34b655…2a6f

4 touches
1 conflict

0x024e57bf…c4a0

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 0x64aaadbf0a…79f9f3

← previous block·next block →recent activity