← previous blocknext block →recent activity

Analyzing

Block #90,821,711

13 transactions · 13 stateful · 2026-07-27 16:40:06 UTC

Parallelism

69/100

Blocked

31%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,821,711  ·  13 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

0x74f95963…01a2

0x34b655…2a6f

6 touches
3 conflicts

0x0d488000…3831

0x34b655…2a6f

6 touches
3 conflicts

0x1d6ce97a…901b

0x34b655…2a6f

4 touches
1 conflict

0x2267f8c4…a571

0x34b655…2a6f

4 touches
1 conflict

0x36a76bd2…1fb0

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5c88208a…cd3a

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

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 0x74f9596374…0201a2

← previous block·next block →recent activity