← previous blocknext block →recent activity

Analyzing

Block #89,538,848

20 transactions · 19 stateful · 2026-07-23 01:27:38 UTC

Parallelism

80/100

Blocked

42%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,538,848  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6bfc7921…ffc8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x405da62e…192a

0xa6afd3…d132

4 touches
1 conflict

0x1ea12d25…e04c

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x711ceb8d…5202

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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

3 conflicts on slot 0x6bfc7921dc…a4ffc8

← previous block·next block →recent activity