← previous blocknext block →recent activity

Analyzing

Block #89,280,770

30 transactions · 21 stateful · 2026-07-21 20:43:02 UTC

Parallelism

87/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,280,770  ·  30 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb6ed530c…d450

0x34b655…2a6f

6 touches
3 conflicts

0x52e69143…95ad

0x065c9d…c394

4 touches
1 conflict

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd6bd849a…5597

0x2a68ba…90c5

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x616c7c23…14e7

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity