← previous blocknext block →recent activity

Analyzing

Block #89,855,335

7 transactions · 7 stateful · 2026-07-24 07:18:12 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,855,335  ·  7 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

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x1a511276…c0d9

0x34b655…2a6f

4 touches
1 conflict

0x59e4ffbf…f01b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x0494220d…abf7

0x34b655…2a6f

2 touches
0 conflicts

0x0b56d384…2178

0x34b655…2a6f

2 touches
0 conflicts

0x184e3288…9044

0x34b655…2a6f

2 touches
0 conflicts

0x1c49bd0b…1a12

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 0x482471adbb…39122f

← previous block·next block →recent activity