← previous blocknext block →recent activity

Analyzing

Block #90,458,824

12 transactions · 12 stateful · 2026-07-26 10:14:25 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,458,824  ·  12 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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xface65c9…44ef

0x34b655…2a6f

4 touches
1 conflict

0xa279b18d…63bc

0x34b655…2a6f

4 touches
1 conflict

0xb5a47a02…d364

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xdd38f4e6…586c

0x34b655…2a6f

4 touches
1 conflict

0xdd38f4e6…586d

0x34b655…2a6f

4 touches
1 conflict

0xf2b035ef…4746

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity