← previous blocknext block →recent activity

Analyzing

Block #89,664,571

24 transactions · 18 stateful · 2026-07-23 15:14:47 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.79

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,664,571  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xafb8e71e…9285

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xda27c764…7fab

0x34b655…2a6f

6 touches
3 conflicts

0x4dc6cd61…f674

0x34b655…2a6f

6 touches
3 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

4 touches
1 conflict

0x6ae4e819…1077

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0xafb8e71eb0…ec9285

← previous block·next block →recent activity