← previous blocknext block →recent activity

Analyzing

Block #90,029,875

13 transactions · 13 stateful · 2026-07-24 21:56:46 UTC

Parallelism

77/100

Blocked

31%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,029,875  ·  13 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

0x45ea7a97…bbb3

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc5031114…58ac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xf4a125dd…5e78

0x34b655…2a6f

4 touches
1 conflict

0xf9e23360…8ef7

0x34b655…2a6f

4 touches
1 conflict

0xfaf3835b…98c7

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 0x45ea7a9723…bdbbb3

← previous block·next block →recent activity