← previous blocknext block →recent activity

Analyzing

Block #90,437,525

9 transactions · 9 stateful · 2026-07-26 08:26:44 UTC

Parallelism

78/100

Blocked

22%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,437,525  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x2c390858…b1ed

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

2 touches
0 conflicts

0x09a168cc…dcc0

0x34b655…2a6f

2 touches
0 conflicts

0x0a906ba5…2454

0x34b655…2a6f

2 touches
0 conflicts

0x12bc05e5…2456

0x34b655…2a6f

2 touches
0 conflicts

0x188330c3…4c83

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0xc824469a90…af6425

← previous block·next block →recent activity