← previous blocknext block →recent activity

Analyzing

Block #90,784,861

12 transactions · 11 stateful · 2026-07-27 13:34:35 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,784,861  ·  12 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

0xbb322930…ace5

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xc6b604e6…5152

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x9ff6033d…37b5

0x34b655…2a6f

4 touches
1 conflict

0x95c47f03…f1bb

0x34b655…2a6f

4 touches
1 conflict

0x0a005879…de60

0x34b655…2a6f

4 touches
1 conflict

0x0c33bb29…c6a9

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 0xbb32293008…46ace5

← previous block·next block →recent activity