← previous blocknext block →recent activity

Analyzing

Block #89,545,502

20 transactions · 18 stateful · 2026-07-23 02:12:06 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

0.95

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #89,545,502  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x41377979…0a18

0x34b655…2a6f

4 touches
1 conflict

0xd1a8b9bd…6f8c

0x34b655…2a6f

4 touches
1 conflict

0x4e089204…52fb

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

6 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity