← previous blocknext block →recent activity
Analyzing
Block #86,923,773
20 transactions · 19 stateful · 2026-07-10 21:58:19 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,923,773 · 20 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
1w02w13w24w39w010w111w212w213w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x15336fe3…1f37
0x34b655…2a6f
6 touches
3 conflicts
0xe8c70616…ed53
0x34b655…2a6f
6 touches
3 conflicts
0xf4a27876…b09c
0x34b655…2a6f
6 touches
3 conflicts
0xe8c70616…ed52
0x34b655…2a6f
6 touches
3 conflicts
0xe7903e6c…8e6e
0x34b655…2a6f
4 touches
2 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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity