← previous blocknext block →recent activity

Analyzing

Block #90,804,256

17 transactions · 15 stateful · 2026-07-27 15:12:12 UTC

Parallelism

76/100

Blocked

27%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,804,256  ·  17 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

0xd2d3fe13…b827

0x34b655…2a6f

4 touches
1 conflict

0xe36d86ef…7486

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xd2d3fe13…b828

0x34b655…2a6f

4 touches
1 conflict

0x3e30b62f…475a

0x34b655…2a6f

4 touches
1 conflict

0x41377979…0a18

0x34b655…2a6f

4 touches
1 conflict

0x428b6e5b…8909

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

1 conflict on slot 0xd2d3fe1336…0db827

← previous block·next block →recent activity