← previous blocknext block →recent activity

Analyzing

Block #89,700,862

20 transactions · 17 stateful · 2026-07-23 18:18:36 UTC

Parallelism

50/100

Blocked

65%

Avg conflicts / tx

2

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #89,700,862  ·  20 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x22e0cc1d…ad0d

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xcf610ab1…35ad

0x34b655…2a6f

10 touches
10 conflicts

0x08330b36…ae29

0x34b655…2a6f

10 touches
10 conflicts

0xadd9c687…1f8b

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x4ac2a863…cba1

0x34b655…2a6f

8 touches
6 conflicts

0x7aad02c6…b979

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity