← previous blocknext block →recent activity

Analyzing

Block #90,703,648

13 transactions · 12 stateful · 2026-07-27 06:46:03 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,703,648  ·  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

0x07b47a10…27ef

0x34b655…2a6f

6 touches
3 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

6 touches
3 conflicts

0xf4d0bddb…07a4

0x34b655…2a6f

4 touches
1 conflict

0xd19c9d38…b459

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdc568d84…62d9

0x34b655…2a6f

4 touches
1 conflict

0x08330b36…ae29

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

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 0x07b47a10b0…8127ef

← previous block·next block →recent activity