← previous blocknext block →recent activity

Analyzing

Block #91,768,878

15 transactions · 11 stateful · 2026-07-31 00:08:13 UTC

Parallelism

87/100

Blocked

27%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,768,878  ·  15 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x9de538e5…7633

0x34b655…2a6f

4 touches
1 conflict

0x9de538e5…7632

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x00f6a8a7…0e6e

0x34b655…2a6f

4 touches
1 conflict

0xd99d25df…ecd8

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0x68178597…13ad

0x34b655…2a6f

3 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

1 conflict on slot 0x9de538e5e9…927633

← previous block·next block →recent activity