← previous blocknext block →recent activity

Analyzing

Block #90,240,440

17 transactions · 16 stateful · 2026-07-25 15:41:01 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,240,440  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0006

0x0a2fbf…29b1

4 touches
1 conflict

0xbf5e6472…1545

0x0a2fbf…29b1

4 touches
1 conflict

0xbf5e6472…1546

0x0a2fbf…29b1

4 touches
1 conflict

0xbf5e6472…1549

0x0a2fbf…29b1

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x217bd767…b79e

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity