← previous blocknext block →recent activity

Analyzing

Block #86,250,061

24 transactions · 20 stateful · 2026-07-07 18:54:04 UTC

Parallelism

79/100

Blocked

30%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,250,061  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x95523e2a…4c01

0x065c9d…c394

8 touches
6 conflicts

0x77ed432f…fa04

0x065c9d…c394

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb1f0701d…4f4a

0xc8689a…ee79

4 touches
1 conflict

0x5639618d…6388

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity