← previous blocknext block →recent activity

Analyzing

Block #89,693,392

17 transactions · 17 stateful · 2026-07-23 17:40:58 UTC

Parallelism

88/100

Blocked

24%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,693,392  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xa47b7766…ee6e

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xef048f92…572b

0x34b655…2a6f

4 touches
1 conflict

0xfb4f6c11…7103

0x34b655…2a6f

4 touches
1 conflict

0x14fe1598…d0ba

0x34b655…2a6f

4 touches
1 conflict

0x4147b177…c9ba

0x34b655…2a6f

4 touches
1 conflict

0xe870e232…7369

0xf9b0c8…8081

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

1 conflict on slot 0xa47b776601…7cee6e

← previous block·next block →recent activity