← previous blocknext block →recent activity

Analyzing

Block #89,858,177

28 transactions · 25 stateful · 2026-07-24 07:32:29 UTC

Parallelism

75/100

Blocked

56%

Avg conflicts / tx

1.29

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,858,177  ·  28 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

0x00000000…0002

0x48cba2…b48b

14 touches
21 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x2491d756…b71c

0xa6afd3…d132

6 touches
3 conflicts

0x2b5101ac…090b

0x34b655…2a6f

6 touches
3 conflicts

0x6847107a…f468

0xa6afd3…d132

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x03aa8b26…118a

0x34b655…2a6f

4 touches
1 conflict

0x33175a5b…a435

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: 0x48cba278…e2b48b

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity