← previous blocknext block →recent activity

Analyzing

Block #90,235,166

16 transactions · 14 stateful · 2026-07-25 15:14:25 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,235,166  ·  16 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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0xfe498a85…9dc4

0x34b655…2a6f

6 touches
3 conflicts

0x410c23da…5793

0x34b655…2a6f

4 touches
1 conflict

0x4d0252db…9ddb

0x34b655…2a6f

4 touches
1 conflict

0x755b0df4…f57e

0x34b655…2a6f

4 touches
1 conflict

0x81f842e8…939f

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity