← previous blocknext block →recent activity

Analyzing

Block #90,441,022

28 transactions · 23 stateful · 2026-07-26 08:44:36 UTC

Parallelism

64/100

Blocked

57%

Avg conflicts / tx

1.64

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #90,441,022  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

16 touches
28 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0x41f1e2e5…2edf

0x34b655…2a6f

12 touches
15 conflicts

0xc5cd29c9…431b

0x34b655…2a6f

8 touches
6 conflicts

0xd235604e…531d

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x91cdfdeb…7feb

0x34b655…2a6f

6 touches
3 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

28 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity