← previous blocknext block →recent activity

Analyzing

Block #89,747,085

18 transactions · 17 stateful · 2026-07-23 22:11:59 UTC

Parallelism

56/100

Blocked

53%

Avg conflicts / tx

1.06

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #89,747,085  ·  18 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x15f968a7…905e

0x34b655…2a6f

6 touches
3 conflicts

0x16891dd2…6254

0x34b655…2a6f

4 touches
1 conflict

0x1ac1c6bd…58eb

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

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 0xac2a02739b…81721b

← previous block·next block →recent activity