← previous blocknext block →recent activity

Analyzing

Block #90,856,710

18 transactions · 17 stateful · 2026-07-27 19:36:09 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,856,710  ·  18 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

0xc9cf85c6…92de

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xa3f095f5…bd87

0x34b655…2a6f

6 touches
3 conflicts

0xc6b604e6…5152

0x34b655…2a6f

6 touches
3 conflicts

0xc3738833…36ca

0x34b655…2a6f

6 touches
3 conflicts

0x658d8194…6914

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

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 0xc9cf85c6ba…3292de

← previous block·next block →recent activity