← previous blocknext block →recent activity
Analyzing
Block #86,320,057
28 transactions · 26 stateful · 2026-07-08 02:41:24 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,320,057 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w39w010w116w318w219w123w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x79108c85…86fd
0xd32edf…ff58
7 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xe360b8bd…6a10
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xb1526c23…f2b5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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: MarginAccount
6 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity