← previous blocknext block →recent activity

Analyzing

Block #89,698,984

18 transactions · 18 stateful · 2026-07-23 18:09:09 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,698,984  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x424934c8…f2f1

0x34b655…2a6f

8 touches
6 conflicts

0x98212952…9ba6

0x34b655…2a6f

8 touches
6 conflicts

0x7a2c83a3…a29a

0x34b655…2a6f

8 touches
6 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

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

6 conflicts on slot 0x424934c865…4af2f1

← previous block·next block →recent activity