← previous blocknext block →recent activity

Analyzing

Block #89,773,836

17 transactions · 17 stateful · 2026-07-24 00:27:04 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,773,836  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x2b17ed65…ecf8

0x34b655…2a6f

6 touches
3 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

4 touches
1 conflict

0x640180aa…dc3a

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

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 0x2b17ed65cb…9aecf8

← previous block·next block →recent activity