← previous blocknext block →recent activity

Analyzing

Block #90,879,564

7 transactions · 7 stateful · 2026-07-27 21:31:10 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,879,564  ·  7 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x9a73834c…0f52

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xf05a71a2…4534

0x34b655…2a6f

4 touches
1 conflict

0x14fe1598…d0ba

0x34b655…2a6f

4 touches
1 conflict

0x26d1c221…4d2a

0x34b655…2a6f

4 touches
1 conflict

0x5146b952…a3ca

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 0xc824469a90…af6425

← previous block·next block →recent activity