← previous blocknext block →recent activity

Analyzing

Block #89,596,068

21 transactions · 19 stateful · 2026-07-23 07:49:50 UTC

Parallelism

62/100

Blocked

37%

Avg conflicts / tx

0.71

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #89,596,068  ·  21 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x1bf8d2af…d140

0x34b655…2a6f

4 touches
1 conflict

0x0bcbbcad…fc9c

0x34b655…2a6f

4 touches
1 conflict

0x4360b49f…140d

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x810a3aa2…0227

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