← previous blocknext block →recent activity

Analyzing

Block #89,568,773

18 transactions · 18 stateful · 2026-07-23 04:47:36 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

0.94

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,568,773  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x1941b441…5889

0x34b655…2a6f

6 touches
3 conflicts

0x698bdd4a…d04c

0x34b655…2a6f

6 touches
3 conflicts

0x6e0e8837…2e59

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x02d895f0…2b93

0x34b655…2a6f

6 touches
3 conflicts

0xb07121bc…523d

0x34b655…2a6f

6 touches
3 conflicts

0x322dcd34…8718

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity