← previous blocknext block →recent activity

Analyzing

Block #89,570,745

23 transactions · 22 stateful · 2026-07-23 05:00:49 UTC

Parallelism

74/100

Blocked

36%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,570,745  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x9211e33e…0b61

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x9e70dadd…810d

0x34b655…2a6f

6 touches
3 conflicts

0x9e70dadd…810e

0x34b655…2a6f

6 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

15 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity