← previous blocknext block →recent activity
Analyzing
Block #86,301,491
30 transactions · 26 stateful · 2026-07-08 00:37:17 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,301,491 · 30 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
1w02w13w25w06w17w09w214w116w318w021w123w424w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xcecf7671…41b6
0xd32edf…ff58
7 touches
6 conflicts
0x8beaeb9d…eec0
0x065c9d…c394
7 touches
6 conflicts
0xba5743c7…21bf
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 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: MarginAccount
6 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity