← previous blocknext block →recent activity

Analyzing

Block #89,545,110

21 transactions · 20 stateful · 2026-07-23 02:09:30 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,545,110  ·  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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xb900efa2…8624

0x34b655…2a6f

6 touches
3 conflicts

0x6a6e42c5…9438

0x34b655…2a6f

4 touches
1 conflict

0x89c4fedf…b214

0x34b655…2a6f

4 touches
1 conflict

0x89c4fedf…b215

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7212

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 0x482471adbb…39122f

← previous block·next block →recent activity