← previous blocknext block →recent activity

Analyzing

Block #90,276,435

16 transactions · 15 stateful · 2026-07-25 18:42:33 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,276,435  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x2ecf1f31…9a68

0x34b655…2a6f

4 touches
1 conflict

0x2fd12b6c…02cc

0x34b655…2a6f

4 touches
1 conflict

0x349f436e…80e6

0x34b655…2a6f

4 touches
1 conflict

0x403fb46d…0d5a

0x34b655…2a6f

4 touches
1 conflict

0x403fb46d…0d5b

0x34b655…2a6f

4 touches
1 conflict

0x49d544eb…9d13

0x34b655…2a6f

4 touches
1 conflict

0x5e8ddd73…4dfb

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity