← previous blocknext block →recent activity

Analyzing

Block #89,865,139

21 transactions · 21 stateful · 2026-07-24 08:07:31 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

1.29

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,865,139  ·  21 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

14 touches
21 conflicts

0xa86351b8…2c5a

0x34b655…2a6f

10 touches
10 conflicts

0x5571e830…9cea

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x350e5d8a…601f

0x34b655…2a6f

4 touches
1 conflict

0x57330c5d…9973

0x34b655…2a6f

4 touches
1 conflict

0x5eb187dd…b1d6

0x34b655…2a6f

4 touches
1 conflict

0x7e17e82a…9748

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity