← previous blocknext block →recent activity

Analyzing

Block #89,827,496

29 transactions · 25 stateful · 2026-07-24 04:57:51 UTC

Parallelism

72/100

Blocked

48%

Avg conflicts / tx

1.14

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #89,827,496  ·  29 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x5a100ac0…96d3

0x34b655…2a6f

8 touches
6 conflicts

0x7775bebd…f690

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x363a4317…87d2

0x34b655…2a6f

4 touches
1 conflict

0x5af098c7…4806

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

21 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity