← previous blocknext block →recent activity

Analyzing

Block #90,689,927

23 transactions · 21 stateful · 2026-07-27 05:37:02 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,689,927  ·  23 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xaa9f27b0…9cf2

0x34b655…2a6f

6 touches
3 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

6 touches
3 conflicts

0x4d4b1184…9b5d

0x34b655…2a6f

6 touches
3 conflicts

0x342358e9…87c6

0x34b655…2a6f

4 touches
1 conflict

0x6017cc43…8173

0x34b655…2a6f

4 touches
1 conflict

0x71892c70…660d

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

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity