← previous blocknext block →recent activity

Analyzing

Block #89,572,329

21 transactions · 18 stateful · 2026-07-23 05:11:23 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,572,329  ·  21 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

0x10797f0b…439a

0x34b655…2a6f

4 touches
1 conflict

0x1a29f452…d890

0x34b655…2a6f

4 touches
1 conflict

0x22e7ebfe…1293

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e65

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x34d95d94…3a16

0x34b655…2a6f

4 touches
1 conflict

0x4560e5a8…b741

0x34b655…2a6f

4 touches
1 conflict

0x58620f29…db5a

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

1 conflict on slot 0x10797f0bd2…dc439a

← previous block·next block →recent activity