← previous blocknext block →recent activity

Analyzing

Block #89,573,900

17 transactions · 17 stateful · 2026-07-23 05:21:51 UTC

Parallelism

82/100

Blocked

18%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,573,900  ·  17 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

0xb5c7c6aa…fdba

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x4886b3df…67a3

0x34b655…2a6f

4 touches
1 conflict

0x4f1ad4b4…e00a

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9db3090e…7fb8

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 0xb5c7c6aad4…acfdba

← previous block·next block →recent activity