← previous blocknext block →recent activity

Analyzing

Block #86,566,090

31 transactions · 23 stateful · 2026-07-09 06:06:01 UTC

Parallelism

90/100

Blocked

26%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,566,090  ·  31 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

0x52e69143…95ad

0x065c9d…c394

4 touches
1 conflict

0x89aae5a8…e220

0x34b655…2a6f

4 touches
1 conflict

0xb550a5df…fbe9

0x34b655…2a6f

4 touches
1 conflict

0xb6ed530c…d450

0x34b655…2a6f

4 touches
1 conflict

0xc948dbdc…199a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xce827910…ff22

0x065c9d…c394

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: Kuru Exchange: Market-MON/USDC

1 conflict on slot 0x52e6914362…6e95ad

← previous block·next block →recent activity