← previous blocknext block →recent activity

Analyzing

Block #91,764,611

15 transactions · 13 stateful · 2026-07-30 23:46:45 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,764,611  ·  15 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x0d759c8b…b9b2

0x34b655…2a6f

6 touches
3 conflicts

0x4f1ad4b4…e00a

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8bddb6c6…c7b0

0x34b655…2a6f

4 touches
1 conflict

0x9a73834c…0f51

0x34b655…2a6f

4 touches
1 conflict

0x9a73834c…0f52

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 0x482471adbb…39122f

← previous block·next block →recent activity