← previous blocknext block →recent activity

Analyzing

Block #89,384,254

21 transactions · 20 stateful · 2026-07-22 08:14:43 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,384,254  ·  21 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

0x82109f73…b6a1

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb34c1337…614c

0x065c9d…c394

4 touches
1 conflict

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x11c14a18…9d3c

0x34b655…2a6f

4 touches
1 conflict

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0x28f324ed…9db7

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 0x82109f73cc…6ab6a1

← previous block·next block →recent activity