← previous blocknext block →recent activity

Analyzing

Block #89,752,751

16 transactions · 15 stateful · 2026-07-23 22:40:36 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,752,751  ·  16 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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xf219f7cf…7379

0xa6afd3…d132

4 touches
1 conflict

0x40502756…179c

0x3bd359…433a

4 touches
1 conflict

0x997ccc40…4dfd

0x3bd359…433a

4 touches
1 conflict

0x00000000…0003

0x48cba2…b48b

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x482471ad…122f

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity