← previous blocknext block →recent activity

Analyzing

Block #90,815,047

22 transactions · 21 stateful · 2026-07-27 16:06:34 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,815,047  ·  22 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

0x6bdb9869…7558

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x4bc1abab…5874

0x34b655…2a6f

5 touches
3 conflicts

0x6ba1eca0…e96f

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

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 0x6bdb9869c7…427558

← previous block·next block →recent activity