← previous blocknext block →recent activity

Analyzing

Block #89,734,817

21 transactions · 19 stateful · 2026-07-23 21:09:58 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,734,817  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x4c572810…b89b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xbb8dc535…4fe7

0x34b655…2a6f

6 touches
3 conflicts

0xa3ed5a09…c6d3

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xee814b91…3428

0xd32edf…ff58

5 touches
3 conflicts

0x53699236…fede

0x34b655…2a6f

4 touches
1 conflict

0xc6fa5268…6ae0

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 0x4c57281054…b4b89b

← previous block·next block →recent activity