← previous blocknext block →recent activity

Analyzing

Block #89,568,573

20 transactions · 15 stateful · 2026-07-23 04:46:15 UTC

Parallelism

90/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,568,573  ·  20 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x16bf0388…fdbc

0x34b655…2a6f

4 touches
1 conflict

0x3b6e959d…158f

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x22af2208…099e

0x34b655…2a6f

2 touches
0 conflicts

0x2d7b3d63…c856

0x34b655…2a6f

2 touches
0 conflicts

0x30c5329c…711c

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x16bf03885e…9cfdbc

← previous block·next block →recent activity