← previous blocknext block →recent activity

Analyzing

Block #90,887,761

20 transactions · 17 stateful · 2026-07-27 22:12:24 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,887,761  ·  20 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

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0001

0xfa32f9…f3f0

6 touches
3 conflicts

0x38b5b2ce…c5bb

0xfa32f9…f3f0

6 touches
3 conflicts

0x16eb5040…a048

0x34b655…2a6f

6 touches
3 conflicts

0x9a8af3c2…e4ae

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

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

6 conflicts on slot 0xd66696e0dc…230842

← previous block·next block →recent activity