← previous blocknext block →recent activity

Analyzing

Block #89,858,687

19 transactions · 16 stateful · 2026-07-24 07:35:03 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,858,687  ·  19 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

0x2840c278…bbc7

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xac4f9a52…35e4

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xa4610db8…cad4

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7214

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 0x2840c278a3…01bbc7

← previous block·next block →recent activity