← previous blocknext block →recent activity

Analyzing

Block #89,599,318

20 transactions · 18 stateful · 2026-07-23 08:11:32 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,599,318  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xbb162541…2f0c

0x34b655…2a6f

6 touches
3 conflicts

0xb8644937…ed09

0x851145…3f07

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x861e5aef…d32c

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eeb

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eec

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 0xc824469a90…af6425

← previous block·next block →recent activity