← previous blocknext block →recent activity

Analyzing

Block #86,219,778

25 transactions · 24 stateful · 2026-07-07 15:31:44 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,219,778  ·  25 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

0x77ed432f…fa04

0x065c9d…c394

6 touches
3 conflicts

0x95523e2a…4c01

0x065c9d…c394

6 touches
3 conflicts

0x077d58c3…8ed7

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x3891cd1c…e740

0x34b655…2a6f

4 touches
1 conflict

0x40bc17c1…8801

0x34b655…2a6f

4 touches
1 conflict

0x41be9e75…9773

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity