← previous blocknext block →recent activity

Analyzing

Block #89,668,806

14 transactions · 11 stateful · 2026-07-23 15:36:21 UTC

Parallelism

86/100

Blocked

18%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,668,806  ·  14 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

0x28e32856…45f6

0x34b655…2a6f

4 touches
1 conflict

0x70b7b52e…7743

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xfc0e8d5c…cfe6

0x34b655…2a6f

4 touches
1 conflict

0x0a57a2b8…3cdd

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xbc4591c1…d562

0x34b655…2a6f

3 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 0x28e32856a1…7845f6

← previous block·next block →recent activity