← previous blocknext block →recent activity

Analyzing

Block #90,789,513

23 transactions · 19 stateful · 2026-07-27 13:58:02 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,789,513  ·  23 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

0x00000000…0002

0x48cba2…b48b

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x48e3acd8…cf41

0x34b655…2a6f

4 touches
1 conflict

0x4b31140b…fd2c

0x34b655…2a6f

4 touches
1 conflict

0x9334a7e7…6f8c

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810d

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810e

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