← previous blocknext block →recent activity

Analyzing

Block #89,664,605

24 transactions · 20 stateful · 2026-07-23 15:14:58 UTC

Parallelism

79/100

Blocked

40%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,664,605  ·  24 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

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xddc22bc2…7f7a

0x754704…b603

6 touches
3 conflicts

0x11b69a7e…334e

0xee8c0e…1242

6 touches
3 conflicts

0xfafe8389…3f20

0x754704…b603

5 touches
3 conflicts

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 0x92385428ad…dc6941

← previous block·next block →recent activity