← previous blocknext block →recent activity

Analyzing

Block #86,315,998

23 transactions · 19 stateful · 2026-07-08 02:14:14 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,315,998  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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…003d

0x065c9d…c394

6 touches
3 conflicts

0x27a04273…27c5

0x065c9d…c394

4 touches
1 conflict

0x49cbdb1b…bda4

0x065c9d…c394

4 touches
1 conflict

0xe6f4a326…ec4f

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity