← previous blocknext block →recent activity

Analyzing

Block #86,290,664

25 transactions · 16 stateful · 2026-07-07 23:24:57 UTC

Parallelism

88/100

Blocked

31%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,290,664  ·  25 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

0x99a3a7c1…1e2b

0x0cc9b2…7777

6 touches
3 conflicts

0x00000000…0000

0x019883…2a9a

6 touches
3 conflicts

0x00000000…0002

0x019883…2a9a

6 touches
3 conflicts

0x00000000…0003

0x019883…2a9a

6 touches
3 conflicts

0xa10c86f8…4b74

0x3bd359…433a

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

6 touches
3 conflicts

0xac2a0273…721b

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: MONI (MONI)

3 conflicts on slot 0x99a3a7c17c…081e2b

← previous block·next block →recent activity