← previous blocknext block →recent activity

Analyzing

Block #90,680,669

17 transactions · 17 stateful · 2026-07-27 04:50:28 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.76

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,680,669  ·  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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x146c718c…8a22

0x34b655…2a6f

4 touches
1 conflict

0x1cdfe548…d3aa

0x34b655…2a6f

4 touches
1 conflict

0x2b1a4848…ad1e

0x34b655…2a6f

4 touches
1 conflict

0x3f5831e5…02b2

0x34b655…2a6f

4 touches
1 conflict

0x42e08579…09bb

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