← previous blocknext block →recent activity

Analyzing

Block #86,358,795

27 transactions · 22 stateful · 2026-07-08 07:00:03 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,358,795  ·  27 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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x27a04273…27c5

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0x588ff17c…d55c

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity