← previous blocknext block →recent activity

Analyzing

Block #91,402,899

24 transactions · 22 stateful · 2026-07-29 17:25:54 UTC

Parallelism

79/100

Blocked

36%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,402,899  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0000

0x019883…2a9a

6 touches
3 conflicts

0x00000000…0002

0x019883…2a9a

6 touches
3 conflicts

0x00000000…0003

0x019883…2a9a

6 touches
3 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xa10c86f8…4b74

0x3bd359…433a

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

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: Capricorn: MONI/WMON Pool (1%)

3 conflicts on slot 0x0000000000…000000

← previous block·next block →recent activity