← previous blocknext block →recent activity

Analyzing

Block #90,810,251

15 transactions · 14 stateful · 2026-07-27 15:42:24 UTC

Parallelism

73/100

Blocked

21%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,810,251  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x0e04c4cc…551a

0x34b655…2a6f

4 touches
1 conflict

0x18cf36a6…a3a3

0x34b655…2a6f

4 touches
1 conflict

0x38948e75…437a

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x57b57f51…2449

0x34b655…2a6f

4 touches
1 conflict

0x61e7b277…fee7

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 0x53f393fafd…2a00b9

← previous block·next block →recent activity