← previous blocknext block →recent activity

Analyzing

Block #89,540,181

23 transactions · 23 stateful · 2026-07-23 01:36:32 UTC

Parallelism

61/100

Blocked

61%

Avg conflicts / tx

1.83

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #89,540,181  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xb900efa2…8624

0x34b655…2a6f

10 touches
10 conflicts

0x9dd0a735…4d04

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x206f4379…e08a

0x34b655…2a6f

6 touches
3 conflicts

0x4be9812b…48a9

0x34b655…2a6f

6 touches
3 conflicts

0x9ad325f5…cc43

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity