← previous blocknext block →recent activity

Analyzing

Block #89,677,831

20 transactions · 16 stateful · 2026-07-23 16:22:27 UTC

Parallelism

85/100

Blocked

38%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,677,831  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7f4a1881…7ec3

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x08636046…e60f

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

4 touches
1 conflict

0x59991669…58c6

0x34b655…2a6f

4 touches
1 conflict

0x81561f70…fefd

0x34b655…2a6f

4 touches
1 conflict

0x82290204…3db0

0x34b655…2a6f

4 touches
1 conflict

0xb4e0a934…5fc7

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 0x7f4a188121…527ec3

← previous block·next block →recent activity